Jump to content

User talk:Yaron Koren/Archive 2013 to 2018

From mediawiki.org
Latest comment: 5 years ago by Msnhinet8 in topic open unlimited images

Extension:External Data #get_file_data - filters

Retrieving data from file as following:

{{#get_file_data: 
directory=DF_Artifactory
|file name=Jenkins_ReleaseRepoList.csv
|format=csv
|data=Leyer=1,repo=3 
}} 

When adding filters with hard coded parameter AAA it working:

|filters=1=AAA

BUT, when I and trying to add variable to filters, it NOT working !!! Looks like Return empty...

|filters=1={{#var:CURR_LY}}
|filters=1={{#if: ={{#var:CURR_LY}} | = {{#var:CURR_LY}} }}

Your help would be very much appreciated.

Thank you!

OlgaJ10 11:20, 10 April 2016 (UTC)Reply


Does the call to {{#var:CURR_LY}} display the right thing outside of #get_file_data? Also, I don't understand that 2nd line at all - are you calling #if the right way? Yaron Koren (talk) 13:18, 10 April 2016 (UTC)Reply

Yes, display correct value outside of #get_file_data.

#if condition also working outside of #get_file_data.

OlgaJ10 11:20, 10 April 2016 (UTC)Reply

I still have no idea what that 2nd line is supposed to do, so I'll just ignore it. But the 1st line should work. Please put that call to {{#var:CURR_LY}} outside of #get_file_data again, then do a "View source" in the browser - does it really just display a simple string like "AAA", or is there a little bit more before or after that in the output, like a <p> tag or something? Yaron Koren (talk) 18:02, 11 April 2016 (UTC)Reply

Reproducing the createPage functionality from SF_CreatePageJob.php

Hi Yaron, I apologize if this is not the right venue to ask, and for my persistence in seeking your guidance. I think I now understand the code in SF_CreatePageJob but I still don't know how I could use it in a hook to get the functionality I want: I'd like all red links to have their pages created automatically once an article is saved. I tried this syntax, but it didn't work: $wgHooks['ArticleSaveComplete'][] = 'SF_CreatePageJob.run()';

Your help would be very much appreciated. Thank you! (Robolobster)

That's C- (or Java-)style syntax - 'SF_CreatePageJob::run' might work better instead. Yaron Koren (talk) 11:56, 12 March 2014 (UTC)Reply

Tour of Consumer Reports' laboratories

Wow! Laboratory tour!

You live in NYC, do you not, Yaron? On Tuesday January 15 at 3pm Wikipedians are invited to join a tour of laboratories at en:Consumer Reports in Yonkers. If you would like to attend please RSVP at en:Wikipedia:Meetup/NYC/January 2013. If you have questions feel free to ask on that page or contact me on my talk page or by my office phone at 914.378.2684. Thank you. Blue Rasberry (talk) 19:48, 9 January 2013 (UTC)Reply

Wow! Laboratory tour! Yaron Koren (talk) 20:03, 9 January 2013 (UTC)Reply

Hi, I am one of the admins of the Site www.pflegewiki.de (ist an Wiki for nurses). We use your Extension Admin Link. To talk about the project wie use an group in google+, so my idea was to add an link in Admin Link. But I have no idea how.... pleas help me! THX Dave (schallopp@pflegewiki.de)

I just answered your similar question on the Admin Links talk page. Yaron Koren (talk) 16:02, 2 April 2013 (UTC)Reply

GSoC / OPW IRC AllHands this week

Hi, you are invited to the GSoC / OPW IRC AllHands meeting on Wednesday, June 26, 2013 at 15:00 UTC (8:30pm IST, 8am PDT) at #wikimedia-office. We have done our best finding a time that works decently in as many timezones as possibles. Please confirm at qgil@wikimedia.org so I can add you to the calendar invitation and I have your preferred email for other occasions. If you can't make it's fine, but let me know as well. We have left a notice to all students, but your help is welcome making sure yours is aware about it. Thank you!--Qgil (talk) 20:24, 24 June 2013 (UTC)Reply

Extension:Header_Tabs question

Hello - Please excuse me for the interruption.

I find that asking questions on the talk pages of extensions often get unanswered.

I absolutely LOVE your extension, and I just was hoping if you had a minute if you could answer this simple question?

I am confused where the body tag is located.

RE: In the 'skins-yui' folder, create a new skin class (for example: yui-skin-sam) to the <body> tag.

Where is the <body> tag? In combined-history-min.js?

I really appreciate your time. Have a great weekend. Igottheconch (talk) 17:15, 5 September 2013 (UTC)Reply

I just answered your similar question on the Header Tabs talk page. Yaron Koren (talk) 17:45, 5 September 2013 (UTC)Reply
thank you! hoping to stay with 1.16 and not upgrade. Appreciate your time! Igottheconch (talk) 19:14, 5 September 2013 (UTC)Reply


Extension:Semantic Forms/Creating query forms

15:50, 22 November 2013‎ Yaron Koren (talk | contribs)‎ . . (3,638 bytes) (-130)‎ . . (Rejected the last text change (by Hans Oleander) and restored revision 782233 by Daniel K. Schneider: "[ and ]" refers to the square bracket characters "[" and "]". I agree it's a little confusing...) (undo | thank) [automatically checked]

Ah, ok - sorry then for deleting this, thought it was some accidental leftover. Using quotes ("[" and "]") like in your comment might make that obvious. - What was the reason to not accept this paragraph: "Another possibility is to embed a default value in the actual query form, using the default=value parameter in the field definition."? It had taken me a while to figure this out, as the char entity trick mentioned before did not work for internal (double square bracket) links in my case, only by constructing an external (single square bracket) link.--Hans Oleander (talk) 16:53, 22 November 2013 (UTC)Reply
Hi - yes, quotes would probably be better; they were left out because some people, when they see quotes, think that the quotes should go into the wikitext... you can't win. :( Anyway, sorry that, by rejecting that edit, I rejected the other change you made, which seems perfectly valid. I just added it in again, modified slightly. Yaron Koren (talk) 18:20, 22 November 2013 (UTC)Reply

Multilingual SemanticMediaWiki

Hi, have you seen the latest versions of this proposal? Its scope seems much clearer to me now. Are you willing to mentor it? --Nemo 10:00, 6 March 2014 (UTC)Reply

I don't think it's entirely clear yet (see the "More thinking is required..." part), but yes, I'd be willing to help out. I'm already a mentor for one project and a co-mentor for another, and I don't know if you're allowed to be a mentor for more than two projects, but even if all three projects get accepted, I could help out either officially or unofficially. Yaron Koren (talk) 12:47, 6 March 2014 (UTC)Reply
Fantastic! An applicant would help with the "more thinking" part. :) I don't think being (co-)mentor for many projects is a formal problem, it's more a problem of capacity on your end. If there are many applications we'll figure out some solution. --Nemo 12:56, 6 March 2014 (UTC)Reply

Please check my answer about "query string"

Extension_talk:Semantic_Forms#Hi.21_Yaron.21 here is my question!

Alright, I checked it. :) Yaron Koren (talk) 22:25, 2 July 2014 (UTC)Reply

Question

Hello. Why Referata has a lot of spam? 190.33.67.43 18:46, 16 August 2014 (UTC)Reply

Regarding Approved Revs extension installation

Hi Yaron,

I have installed “Extension: Approved Revs” to prevent publishing changes to a page until approval and followed the steps mentioned in the MediaWiki for that. But after the installation I still could not see the (approve) link on history page and also the changes made on the pages are published directly to all the users.

Below are the changes I did for the extension installation.

1. Created a folder “ApprovedRevs” inside extension folder and copied all the files.
2. Executed the DB scripts to create the DB objects
3. Added the below configuration in the LocalSettings PHP file
     require_once( "$IP/extensions/ApprovedRevs/ApprovedRevs.php" );
     $wgGroupPermissions['*']['edit'] = false;
     $egApprovedRevsBlankIfUnapproved = true;
     $wgGroupPermissions['*']['viewlinktolatest'] = false;
     $wgGroupPermissions['sysop']['viewlinktolatest'] = true;
     $egApprovedRevsAutomaticApprovals = false;
     $egApprovedRevsShowApproveLatest = true;


Am I missing anything? Appreciate your help on this. Thanks

Regards Gopi. R

Does Approved Revs show up in your Special:Version page? And are you looking at pages in the main namespace? Yaron Koren (talk) 04:40, 3 November 2014 (UTC)Reply


Are you asking about special pages? I checked the special pages and its not showing the Approved Revs. Also I’m looking at the pages which are created newly for my site not in the main page.
The question is whether the extension is listed on the page Special:Version in your wiki. This page will have a table with the installed extensions. Is ApprovedRevs there? --88.130.112.113 16:23, 3 November 2014 (UTC)Reply

I could not find the page Special:Version on my wiki and I can see only "special pages" on the left navigation.

This one: Special:Version. But in your wiki. --88.130.80.53 22:01, 3 November 2014 (UTC)Reply

Still I could not locate this page on my wiki. Could you advise me if there any way to find(navigate) to this page?

Blank page after installing Widgets in 1.24.1

Hi Yaron,

I am configure a wikifarm based on semantic mediawiki, every wiki shares the same code using symlinks. Everything looks fine but I get a blank page when I configure the Widgets extension. Could you have some idea about this issue?

Thank you very much for your support.

Hi - see here for how to see the error message when you get a blank page. Yaron Koren (talk) 00:34, 12 January 2015 (UTC)Reply
Thank you Yaron, I found the problem based on your suggestion.

¡Una barnstar para ti!

El Barnstar original
Thank very much Yaron NancyGertrudiz (talk) 02:10, 14 January 2015 (UTC)Reply

Hey, gracias! Yaron Koren (talk) 02:15, 14 January 2015 (UTC)Reply

SF: Invalid or virtual namespace -1 given

Hi Yaron, I am carry on to configure a semantic wikifarm. Rigth now, I get the error when user try to create a new page using semantic forms. I had installed Semantic Forms using composer. Could you give some directions about how to solve this issue? Thank you

At what point in the process do you get the error? And is the page you're trying to create in a custom namespace? Yaron Koren (talk) 22:27, 15 January 2015 (UTC)Reply

We get the error when it tries to create the page in a custom space. Even the admin user get the same error. Thank you

Alright. What happens if you try to create a page in that namespace, without a form? Yaron Koren (talk) 00:08, 16 January 2015 (UTC)Reply

It works create a simple page in custom namespaces, the issue appears when we use SemanticForm even in Main space.

On the page where the form is displayed, what does the URL look like? Yaron Koren (talk) 00:19, 16 January 2015 (UTC)Reply

I'll send you by e-mail.

Hi Yaron, the issue is generated by Extension:ConfirmEdit, it was a version conflict. Everything ok. Thank you

Oh, great. Yaron Koren (talk) 23:44, 18 January 2015 (UTC)Reply

i'm getting this as well from Confirm edit (latest), and sforms(3.2-alpha(latest)). It gives the error at the top of the form when i hit the save page button. Guess i'm going to try some old versions of confirmedit based on what other user said. http://i.imgur.com/1q1rQdp.png

Yup the problem was using a new version of confirm edit with old version of mediawiki. When i got the confirm edit branch for my version of mediawiki the problem went away (mediawiki 1.23, cloned branch wmf/1.23f22wmf)

FURTHER COMMENT Hi Yaron, I am getting the same error. My site uses the following most recent stable versions - Mediawiki 1.25.1, Semantic Forms 3.2 (9a0fbae), Semantic MediaWiki 2.2 and Confirm Edit 1.3. The exact error message is "Invalid or virtual namespace -1 given". The namespace ID "-1" is the default system ID for the "Media" namespace. It happens whenever a form is used to create an article and whether logged in as Sysop or User. It is a recent error which occurred when I updated from Mediawiki 1.24.7 and also installed the latest versions of Semantic Forms and SMW. Commenting out the call to Confirm Edit extension in my LocalSettings.php file solves the problem, so the conflict is with that extension. In my case, I can manage without the Confirm Edit extension because my site requires approval of user accounts (using the Confirm Account extension) and I don't really need any form of captcha. However, thought the above discussion helped me find the problem and I thought my experience / settings may also help in finding the problem. Cheers, Allen


Has there been any update to this? I'm still getting the error, Invalid or virtual namespace -1 given, with Version 1.25 Confirm Edit & MediaWiki 1.25.2 Thanks

What version of SF? Yaron Koren (talk) 16:56, 8 October 2015 (UTC)Reply

'SF_VERSION', '2.7' I just upgraded to the 3.3.2 and it seems to work fine. I'm not sure why the 2.7 was still included with the most recent SF Bundle download.... Thanks!~!

Me Too!

I'll add my name to this reporting list for the exact same bug:

  • MW = v1.25.1,
  • SF = v2.7,
  • Confirm Edit = v1.3, (Note, sysop does not trigger confirmEdit but still gets the same error message.)

This is rather troubling, because ConfirmAccount is not very resistant to smart vandal-bots, without the use of ConfirmEdit. WmBliss (talk) 22:28, 8 October 2015 (UTC)Reply

Like everyone else getting this error, you are using a very old version of SF - 2.7 - that comes bundled with Semantic Bundle. (Yes, I know SB has to be updated.) Just upgrade SF. Yaron Koren (talk) 23:13, 8 October 2015 (UTC)Reply
Thank you User:Yaron Koren. That did fix most problems. BTW, you and your book seem to be saving MediaWiki. Are you implying that I should upgrade all the other extensions packaged in the SMW Bundle? If so, should I be installing & using Composer to do this? WmBliss (talk) 15:39, 10 October 2015 (UTC)Reply
I don't if MediaWiki is in any danger, but if my book and I are saving it in some small way, that's great to hear! No, I wasn't implying that - I meant that I, or someone else, needs to update SB to include all the recent versions of everything. If you're not having problems with SMW, for instance, there's no real need to upgrade it. Though if you do want to, then yes, you'd probably have to use Composer at the moment. Yaron Koren (talk) 23:41, 11 October 2015 (UTC)Reply
Sorry, User:Yaron Koren, I know you are probably getting ready for Barcelona, but this problem returned anytime a new page is created using a form created by SF's "Create a Class" or "Create a Form". I'm running, MW 1.25.1, SF 3.2, and Cargo 0.10. ConfirmEdit seems to have no effect. WmBliss (talk) 03:28, 16 October 2015 (UTC)Reply
The fact that a form was created in a certain way shouldn't have any impact. Are you creating pages in a custom namespace, perhaps? Is there anything else going on that's unusual? Yaron Koren (talk) 20:50, 16 October 2015 (UTC)Reply
I made the changes to SF_AutoeditAPI.php, suggested by Gerrit, and that seems to have fixed the problem (we'll see). WmBliss (talk) 15:05, 17 October 2015 (UTC)Reply
Oh - I didn't notice that you were using SF 3.2, and not the latest version, 3.4. Yaron Koren (talk) 23:36, 17 October 2015 (UTC)Reply
Yaron, just to let you know,
  • the "Download snapshot" link on the SF page currently points to ExtensionDistributor which downloads REL1_25-ab27659.tar.gz which in-turn contains SF v3.2.
  • The 'zip' file is v3.3.2
  • It is only the link (Git Master) which points to v3.4.
Should MW administrators consider git to be a mandatory tool? WmBliss (talk) 14:55, 18 October 2015 (UTC)Reply
Oops, I forgot to update the zip file link - sorry about that. I just did it now. Nobody should use that "Download snapshot" link - I wish it weren't there, and I wish it weren't so conspicuous. It's somewhat out of my hands, though; it's set via a standard template. Yaron Koren (talk) 00:46, 19 October 2015 (UTC)Reply

Starting conversion of LiquidThreads to Flow at mediawiki.org

Hello. I'm sending this to you, because you've been one of the top 50 users of LQT on mediawiki.org over the last 360 days,[1] and I wanted to make sure that you'd seen the announcement at Starting conversion of LiquidThreads to Flow at mediawiki.org. There are links in the topic-summary at the top, for other discussions (wikitech-l and Project:Current_issues), and a link to the planned process and timeline (scheduled to begin April 6, with smaller conversions at first). Please do test Flow out at Talk:Sandbox if you haven't tried it recently, and give any feedback/suggestions/requests at that main discussion location. Much thanks, Quiddity (WMF) (talk) 00:02, 28 March 2015 (UTC)Reply

Wiki farm extension

Hi Yaron,
sorry for my simple question, what wiki farm extension you use on Referata?

Thank you, --Bserge77 (talk) 10:10, 21 April 2015 (UTC)Reply

It's "Wiki Garden" - an extension I wrote, that I haven't released yet, but I've been meaning to. Yaron Koren (talk) 14:10, 21 April 2015 (UTC)Reply

Bug: "Edit with form" do not ask what to edit

In Special:SpecialPages under Semantic Forms, the link Edit with form goes directly to Special:FormEdit, it is not asking the user which form name and target page that should be edited so users are not redirected to Special:FormEdit?form=<form name>&target=<target page>", or "Special:FormEdit/<form name>/<target page>.

Even with forms created, users are not asked which form they want to edit with Special:FormEdit which says this twice:

No target page specified.

This is the page for editing with a form. You must specify both a form name and a target page in the URL; it should look like "Special:FormEdit?form=<form name>&target=<target page>", or "Special:FormEdit/<form name>/<target page>".

No target page specified.

This is the page for editing with a form. You must specify both a form name and a target page in the URL; it should look like "Special:FormEdit?form=<form name>&target=<target page>", or "Special:FormEdit/<form name>/<target page>".

You shouldn't click that link in Special:SpecialPages, and I should probably remove it from the page. Yaron Koren (talk) 14:50, 29 May 2015 (UTC)Reply
Yes please, can you remove it and confirm?

A kitten for you!

A kitten for your family, from a member of your MediaWiki family. Thanks again.

WmBliss (talk) 15:41, 10 October 2015 (UTC)Reply

Is it possible to use the Page Schema and the Semantic Form for a very basic tiny dependent DB?

After learning some, and little experiencing the extensions, i try to figure out if i can use it for a just little complex database with dependencies
1-between fields within a template/form (a field X can be filled up only if field Y is already filled up or only if field Y="Accepted") and,
2-between fields in different forms (for instance i want a field to restrict entry to only a name of student which exist in another template/form either as a pagename or just a data record field there). Thanks!

#1 is not possible, but #2 is, using a dropdown and "values from property=" (or "cargo field=" and "cargo table=", if you're using Cargo). Yaron Koren (talk) 07:30, 29 October 2015 (UTC)Reply
I tried the value from namespace= and it works. but the "cargo field=" and "cargo table=" is not. (entered: cargo field=City and cargo table=Popularity). in the Page Schema there is i Form field definition and a Cargo field definition per every field. I tried to dropdown in the Form field and the condition in the Form and alternatively in the Cargo field definition. none of those worked. when entered in the Cargo field definition it just gave me back the option itself "cargo field=City and cargo table=Popularity" in the dropdown box. thanks
Do you have both Cargo and SMW installed, or just Cargo? And what version of Cargo? Yaron Koren (talk) 13:35, 29 October 2015 (UTC)Reply
I had the smw but deleted it. Now i have the cargo last version downloaded this week and the recent SF.
Cargo version 0.1
When i go to edit, is this the required result in the Form edit?: (this isnt working)
</noinclude><includeonly>
<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
{{{for template|CityComplaint}}}
{| class="formtable"
! a: 
| {{{field|a|input type=text}}}
|-
! b: 
| {{{field|b|input type=dropdown|value from cargo table=City and value from cargo field=Popularity}}}
|-
! c: 
| {{{field|c|input type=text}}}
|-
! d: 
| {{{field|d|input type=text}}}
|}
{{{end template}}}

thanks

Replace the " and " with "|". Also, you should definitely upgrade your version of Cargo (and maybe SF too, if that one is also old). Yaron Koren (talk) 14:46, 30 October 2015 (UTC)Reply

Please provide feedback on suggested improvements to the Code of Conduct

Thanks to everyone who’s helped work on the Code of Conduct so far.

People have brought up issues they feel were missed when working on "Unacceptable behavior" and "Report a problem". Consultants have also suggested changes in these same sections.

These are important sections, so please take a look at the proposed changes. I apologize that this feedback arrived later than planned, but I think this will create a better document.

If you prefer to give your opinion privately, feedback via e-mail is welcome at conduct-discussion@wikimedia.org.

Thanks. Mattflaschen-WMF via MediaWiki message delivery (talk) 04:18, 24 February 2016 (UTC)Reply

Shouldn't it be complex?

Hello, Yaron. The business you do is big and the contribution is notable. The question is — aren't you going to combine functionality of PageSchemas, SemanticForms and Semantic MW? The second one just helps the third one, but the first one is just an extension of the second one. In other words, all these are about one subject. Ядерный Трамвай (talk) 22:59, 25 February 2016 (UTC)Reply

There are a variety of reasons why it's better to keep these extensions separate, I would say - one big reason is that Semantic Forms can also work with Cargo, not just SMW. Yaron Koren (talk) 23:57, 25 February 2016 (UTC)Reply

Please participate in discussion on updated "Marginalized and underrepresented groups" text

Thanks for participating in the earlier discussion on Talk:Code of Conduct/Draft#Marginalized and underrepresented groups. There was some support and some issues were raised. I've attempted to propose a better draft to address the issues.

Please participate at Talk:Code of Conduct/Draft#New proposed wording. Thanks. User:Mattflaschen-WMF via MediaWiki message delivery (talk) 01:40, 17 March 2016 (UTC)Reply

Please participate in discussion on updated "Enforcement issues" text

Thanks for participating in the earlier discussion on Talk:Code of Conduct/Draft#Enforcement issues. There was strong support for the first two points, so they have been closed. Most people either supported the third at least in principle, or were neutral. However, there are some suggested wording changes (partly by Smalyshev (WMF), and partly by me).

Please participate again at Talk:Code of Conduct/Draft#New proposed wording. Thanks. User:Mattflaschen-WMF via MediaWiki message delivery (talk) 01:48, 17 March 2016 (UTC)Reply

Please participate in discussion on updated "Enforcement issues" text

Sorry, the correct link for the discussion about wording re Talk:Code of Conduct/Draft#Enforcement issues is Talk:Code of Conduct/Draft#Circumvention text new wording. Thanks. I apologize for the double-message. User:Mattflaschen-WMF via MediaWiki message delivery (talk) 01:51, 17 March 2016 (UTC)Reply

Please reach out to Stewards for your account issues

Thanks. --Jyothis (talk) 16:09, 15 November 2016 (UTC)Reply

RfC: Intersected categories based on SMW

Hallo,

When you have the time, please look at this RfC for Intersected categories based on SMW and comment, if you care to.

I'd like to know if you think this is at all possible to be implemented in an extension, given the current functionality of MW and SMW. Would it be effecient? Would be not too complex to implement in an extension?

Regards, --Ahmad Gharbeia أحمد غربية (talk) 01:08, 11 December 2016 (UTC)Reply

A barnstar for you!

The Technical Barnstar
Super meeting you yesterday Yaron and again thanks so so much for the amazing extensions. We'll be honored if you'd host your wikis at Miraheze. Our IRC channel is #miraheze Sandnerd (talk) 17:20, 12 January 2017 (UTC)Reply

Share your experience and feedback as a Wikimedian in this global survey

Your book - superpages

Hi Yaron, I am just looking at the web site with your new book. It doesn't include any contact info for you so I am contacting you here. You mention super-pages in a heading in the book, but the paragraph doesn't include any info about super-pages. Just wanted to pass it on. Tenbergen (talk) 19:56, 8 March 2017 (UTC)Reply

Thanks for pointing that out! It looks like that error has been around for a while, but no one has pointed it out until now. Yaron Koren (talk) 02:46, 9 March 2017 (UTC)Reply

A barnstar for you!

The Original Barnstar
For your good work on Semantic MediaWiki. :) Alangi derick (talk) 20:50, 20 June 2017 (UTC)Reply

Referata

I'm working on it, sorry. Yaron Koren (talk) 03:32, 10 August 2017 (UTC)Reply
Okay, I think it's fixed now. I have a Facebook account, but I rarely use it. Yaron Koren (talk) 03:55, 10 August 2017 (UTC)Reply

Referata TestWiki

Hello Yaron,

I've emailed you a few times, but I have not heard a response, so I'm going to try and ping you here.

I am the founder of Referata TestWiki. Recently within the last few weeks, there has been a lot of vandalism, disruption, and other abuse. Some of the disruption is coming from sockpuppets, while some of it is just coming from drive-by annoying users. In order to stop this disruption, can you please enable the AbuseFilter and CheckUser extensions on the wiki? AbuseFilter will stop vandalism before it happens, which I really need right now. SmiteSpam and Nuke are only good after vandalism has occurred, but I would like to be able to stop it before it happens. CheckUser will help me identify inappropriate editors (i.e. sockpuppets) and will also help to identity malicious bots and proxies. I have custom-coded a check user widget script but it is not reliable and is nowhere near as sophisticated as the actual CheckUser extension. Therefore , I would like these two extensions to be installed on Referata TestWiki as soon as possible.

I note that CheckUser is already installed on the Main Referata "Meta" site, but I haven't seen AbuseFilter anywhere. I suggest that you install these extensions globally as they are very useful and effective at stopping disruption.

Additionally, can you please globally upgrade the MediaWiki version to at least 1.26 (preferably later) and also install the Scribunto extension? Scribunto allows for pages that require modules, such as userboxes and other templates. I find these very useful.

Also, please fix UserMerge - the tool has been giving internal fatal errors for over a month now.

Sincerely,

Xauroflaux

Founder, Referata TestWiki

A kitten for you!

Thanks a lot for all the hard work you've put into many excellent extensions. Yesterday I tried out Replace Text, and noticed you were the brain behind that one too. Fantastic extension, especially as I can't, after oh so many attempts, successfully install and get AWB running on my Linux rig. Cargo is brilliant too, and I really hope we can merge the whole wiki to it, in due time. Thanks again, and keep up the marvellous work! :)

Pangaearocks (talk) 10:09, 5 September 2017 (UTC)Reply

Thanks! Yaron Koren (talk) 13:48, 5 September 2017 (UTC)Reply

Flow doesn't support all wikitext

Hi. I saw you recently changed the Flow page to say it supports all wikitext. Actually Flow can't even save wikitext. When you preview or save, Flow makes a best-effort to convert the wikitext to HTML then throws away the wikitext. When you return to the wikitext edit screen, Flow makes a best-effort to convert that HTML back to similar wikitext for editing. Speaking as a programmer, I believe the technical term for this is "unholy hack". It simulates wikitext support. This unholy hack results in all sorts of rendering errors and content corruption issues. This round trip translation will randomly re-write supported wikitext, and unsupported wikitext is completely destroyed. Some wikitext gets corrupted in a way that expands like a tumor each time it goes through round trip translation (each time you preview or save&re-edit). It's such an unholy hack that it even manages to break the revert button. Flow never saves the original wikitext, and during the revert process Flow tries to convert the HTML back wikitext. That wikitext can be faulty, and the faulty wikitext gets saved as the revert-result.

I apologize if I got carried away ranting about the issue in excessive detail. Flow's corruptions issues are a pet peeve of mine. Anyway, I changed the Flow page to say it supports most wikitext. The Flow page really should mention "content corruption issues", but members of the Flow team would surely editwar it away. Alsee (talk) 09:23, 6 September 2017 (UTC)Reply

Sorry - I only know a moderate amount about Flow, and I wasn't trying to write anything controversial. Feel free to change anything I wrote. And yes, I agree that the page should mention any bugs that exist. Yaron Koren (talk) 13:27, 6 September 2017 (UTC)Reply

wikifamily.tk

I don't think I can help... I don't know anything about the Monaco skin. Yaron Koren (talk) 14:09, 1 November 2017 (UTC)Reply

Can't access Referata pages

Hi, Yaron Koren. I'm a sysop at a Referata wiki. For the last few weeks or so, there have been certain pages that give me an error when I try to access them. It says:

Fatal error: Call to undefined method LocalFile::setUrl() in /home/yaron57/public_html/w/extensions/WikiGarden/includes/WG_Utils.php on line 250

However, some other pages are normal. Is there anything you can do to fix this? Gfdgsgxgzgdrc 20:17, 13 November 2017 (UTC)Reply

Sorry about that - it was due to a MediaWiki upgrade. I think this is fixed now. Yaron Koren (talk) 03:51, 14 November 2017 (UTC)Reply
Thanks, although some other pages are getting a different error:

Fatal error: Cannot access protected property ThumbnailImage::$url in /home/yaron57/public_html/w/extensions/WikiGarden/includes/WG_Utils.php on line 258

Also, I was wondering if you could install Extension:GetUserName on Referata. It would be useful for a page I'm working on. Gfdgsgxgzgdrc 22:59, 24 November 2017 (UTC)Reply
Could you help, please? Gfdgsgxgzgdrc 00:26, 28 November 2017 (UTC)Reply
Sorry for the delay - I think this, too, is fixed now. As for GetUserName - what's better about that than "CURRENTUSER" from the MyVariables extension? Yaron Koren (talk) 04:10, 4 December 2017 (UTC)Reply
Thanks so much! Everything is fixed now. Also, sorry, I didn't know about CURRENTUSER. I'll use that instead. Thanks for letting me know! Gfdgsgxgzgdrc 01:14, 7 December 2017 (UTC)Reply

Gamepedia dropping SMW support

Hi Yaron. On Gamepedia's help wiki, I noticed that they have decided to drop support for SMW, and are encouraging people to migrate to Cargo instead. I see more interest in Cargo in their Slack community channel, and with this decision, it's quite possible more wikis will move over to Cargo in due time. Figured I'd let you know, but posting here instead of the Cargo talk page. —Pangaearocks (talk) 05:56, 26 November 2017 (UTC)Reply

That's good to know - thanks for letting me know about it. Yaron Koren (talk) 18:25, 26 November 2017 (UTC)Reply
Could be some interesting times ahead, indeed, though I doubt they'll push too hard on the wikis that already are well-integrated with SMW. On another yet similar note, I've made some help pages about Cargo over there, which for the most part have been copied from the help pages here. I hope that is okay, given the note at the top of each page :) Eventually they'll be adapted more for the needs of users there, for instance a more detailed migration guide, perhaps with some advice based on people experience with the process, and perhaps removing installation/setup sections, since normal users/admins don't have access to that anyway. –Pangaearocks (talk) 23:58, 2 December 2017 (UTC)Reply
It looks good. I have no problem with copying over the content, but it means that you'll have to keep updating those pages if you want them to stay fully accurate, which may be a pain for you. Yaron Koren (talk) 04:18, 4 December 2017 (UTC)Reply

Extensão de fóruns

Good Morning. I am a reverser of the brazilian Memeswiki, a wiki under construction. There is a extension that organizes the topics of a forum, wich allows the user to view the most current topics (<forum></forum>). I intend to use this code in the MemesWiki forum, and I need you to indicate the link for this Extension. Thank you. 179.69.24.142 17:45, 28 January 2018 (UTC)Reply

Sorry - I don't think I know of an extension that defines a <forum> tag. Yaron Koren (talk) 23:07, 28 January 2018 (UTC)Reply

Security review of Extension:Replace Text

Hi, We have discussed in Bengali Wikisource to install Extension:Replace Text, but as the extension has not been deployed in any Wikimedia website, the phabricator task has been stalled. It would be great if you please take the necessary steps to security review the extension. Thanks -- Bodhisattwa (talk) 15:26, 7 February 2018 (UTC)Reply

I don't think I'm the right person to do a security review, unfortunately - and definitely not for one of my own extensions. But I'd be happy to help with this process in any way I can. Yaron Koren (talk) 15:34, 7 February 2018 (UTC)Reply

uploadable - images not showing i form result

Dear Yaron

I've made a mediawiki website: midlertidighed.dk

Where I want users to describe their own projects through using a form.

My problem is that the images which are uploaded through the form aren't visible in the reply

The resulting page only shows: |input type=text=1455160_442824492496486_900402639_n.jpg

Is there a way to include the uploaded image on the page?

<noinclude>
Skriv navnet på dit projekt her: 

{{#forminput:form=Skabelon til oprettelse af midlertidige projekter}}

Hvis der allerede er et projekt med det navn, vil du kunne redigere dette.

</noinclude><includeonly>
<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
{{{for template|Skabelon til præsentation af midlertidige projekter}}}
{| class="formtable"
! Navn: 
| {{{field|Navn}}}
|-
! Placering: 
| {{{field|Placering|Coordinates}}}
|-
! Årstal: 
| {{{field|beskrivelse|year}}}
|-
! Upload billede: 
| {{{field|input type=text|uploadable}}}
|}
{{{end template}}}

'''Beskriv projektet'''

{{{standard input|free text|rows=10}}}

{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
</includeonly>
It looks like there are some problems with the form, first of all. I don't speak Danish, but is it correct that the field named "beskrivelse" should be labelled "Årstal", or is that supposed to be two different fields? As for the uploadable field, it lacks a name. Once you get all that fixed, the template needs to be modified - instead of something like "{{{My uploadable field|}}}" at the end, it should look like "[[Image:{{{My uploadable field|}}}]]". Yaron Koren (talk) 21:50, 25 February 2018 (UTC)Reply

Thank you for your reply!

Dear Yaron

Thank you so much for your reply!

OK I figured out that I can edit this section, so no more sections:-)

I edited the form as you described.

But I'm not sure where to put this bit: "[[Image:{{{My uploadable field|}}}]]"

When I put it in the template til just shows [Image:] in the resulting page...

Hm, that's true, it should probably instead by something like: "{{#if:{{{My uploadable field|}}}|[[Image:{{{My uploadable field|}}}]]}}". Yaron Koren (talk) 15:28, 26 February 2018 (UTC)Reply

Referata

Share your experience and feedback as a Wikimedian in this global survey

WMF Surveys, 18:36, 29 March 2018 (UTC)Reply

Submiting of patch

Hi, can you merge patch https://gerrit.wikimedia.org/r/#/c/425722/ so you can merge patch https://gerrit.wikimedia.org/r/#/c/415021/

Thanks! Zoranzoki21 (talk) 23:51, 11 April 2018 (UTC)Reply

Are you sure you meant to write me about this? I have nothing to do with Blue Spice. Yaron Koren (talk) 00:45, 12 April 2018 (UTC)Reply

Reminder: Share your feedback in this Wikimedia survey

WMF Surveys, 01:34, 13 April 2018 (UTC)Reply

Your feedback matters: Final reminder to take the global Wikimedia survey

WMF Surveys, 00:43, 20 April 2018 (UTC)Reply

Consultant?

Yaron,

You've been enormously helpful and active in replying to questions on your different MediaWiki extension pages. I'm currently working on a project, and I think I will eventually get it where I want it, but I'm thinking I could save loads of time and frustration if I could have you consult officially on the project. Would you be available for that kind of consulting? May214 (talk)

I don't do much consulting directly any more, but I have a company, WikiWorks, that can certainly help with whatever you need. You can write info@wikiworks.com about it, or me directly at yaron57@gmail.com. Yaron Koren (talk) 23:17, 20 May 2018 (UTC)Reply

DIQA/Ontoprise code

Did you know about https://github.com/kkthek/diqa-richtext and related repositories? Should we document their existence somewhere? --Nemo 20:52, 11 June 2018 (UTC)Reply

Oh - I knew about DIQA/Ontoprise, but not about this extension. I guess it could be added to Extension:Page Forms/Related extensions, but I don't know whether this extensions still works, or even what it really does - or whether it has been released yet. Do you know any of these things? Yaron Koren (talk) 22:38, 11 June 2018 (UTC)Reply
Indeed I don't. I think it's to import some corporate documentation from Word documents to (structured) wiki pages on private wikis. So it's hard to see it in action anywhere. --Nemo 07:22, 12 June 2018 (UTC)Reply

Defining new inputs...

Hi. The purpose of the Mediawiki installation on my Synology NAS at home is to create something like a management for my music and movie collection. When it comes to programming in general, I'm not so inexperienced. Since 1989 I've done a lot of programming for programmable logic controllers of our machinery at my employers plants. If you don't stick to logic operations you end up in somthing that looks like assembler programming. So this is very different to HLL programming like Java or PHP. From 2011 to 2015 I studied Business Informatics at a local technical college. There I had contact with C and Java. I also fumbled around with a little bit PHP programming. For this wiki MoBaDaten.Info that I run I had to modify several extensions (Guestbook, iDisplay and ImageSizeInfoFunctions), so that they meet my expectations. I also created an extension named TitlesAndTargets. But that gives not the general view to PHP, so I'm surely kind of new to PHP and Mediawiki programming.

For this music and movie management I was looking for something comfortable to insert data and I found the Page Forms extension. But what I'm missing is an input type for time. Not time of day like the undocumented timepicker type. More something to insert a duration (of a music track or a movie). The general idea is to get one or more input fields, configurable for days, hours, minutes, seconds and milliseconds. A little bit like the date type which merges day, month and year to a single value. I think this would be a complement to the existing field types. So I would like to integrate this into the Page Forms code rather than create a stand alone extension.

Maybe I should fumble around with this idea on my Mediawiki installation at home first. There I will see how far I come on my own as a start.--Wgkderdicke (talk) 23:48, 20 July 2018 (UTC)Reply

It sounds like you've had a very interesting career so far! I'm glad you're now getting involved in MediaWiki.
I've thought a duration input type, but I'm not sure how useful it would be - compared to just separate text inputs for seconds, minutes, etc. If you had a template that stored all of these separately, you could have it additionally include a computed value that just held, say, the total number of seconds - so that you could sort on duration and so forth. (If you ever start using Cargo or Semantic MediaWiki, that is - it doesn't look like you're using either of them at the moment.) But I don't see a big advantage to having a "picker" input to select, say, 35 minutes, as opposed to just entering "35" in a "minutes" field. What do you think? Yaron Koren (talk) 00:34, 21 July 2018 (UTC)Reply
Well, I'm not thinking about a "picker" input. In my opinion this would be too cumbersome. I think that the "datetime" input is the nearest existing input to my idea. Now remove the date and AM/PM parts from that input and add inputs for days and milliseconds. I like the idea to hold the value of such input in an integer format. If milliseconds are involved, it may be better to hold the total number of milliseconds. I'm also thinking about a format option, so that one can configure the input. For example, {{{field|foo|input type=time|format=hms}}} will give you three (text) inputs, divided by colons. The first input for hours, the second for minutes and the last one for seconds. With format=dhmsf you will get the complete bunch of inputs (the "f" stands for fraction of seconds, means milliseconds), with format=m you will get only one input for minutes. So one can customize this input a little bit. Illogical combinations like days and seconds only has to be excluded, though. And yes, you're right, I'm using neither Cargo nor Sematic MediaWiki at the moment. To gather some information on my home wiki and on MoBaDaten.Info the DPL3 resp. third party DPL extenstion is at work. This extensions provide also sorting functionalty. --Wgkderdicke (talk) 02:02, 21 July 2018 (UTC)Reply
That went quicker than I thought.
  1. I named this input duration.
  2. I created a file named PF_DurationInput.php with the special code for this input. I stored this file in the forminputs folder.
  3. I added two classes named daysInput and millisecondsInput in the PageForms.css file from the skins folder (line 105 et seq.).
  4. I added a new line in the extension.json file from the extensions base folder after line 152:
    "PFDurationInput": "includes/forminputs/PF_DurationInput.php"
  5. I added a new line in the PageForms.php file from the extensions base folder after line 226:
    $GLOBALS['wgAutoloadClasses']['PFDurationInput'] = __DIR__ . '/includes/forminputs/PF_DurationInput.php';
  6. I added a new line in the PF_FormPrinter.php file from the includes folder after line 60:
    $this->registerInputType( 'PFDurationInput' );
  7. And finally I extended the getStringFromPassedInArray method (line 610 et seq.) in order to store the duration values.
Well, at first glance it seems to work on my home NAS Mediawiki installation. The value is stored as total number of milliseconds. But I'm not so entirely happy with the math. If there are values entered in a form, the total number of milliseconds is calculated by the getStringFromPassedInArray method from the getStringFromPassedInArray class. To display existing values, the total number of milliseconds is picked apart in the PF_DurationInput.php file.
The input is customizable. With the optional format parameter you can choose the following combinations:
f, s, sf, m, ms, msf, h, hm, hms, hmsf, d, dh, dhm, dhms, dhmsf
Depending on the choosen format one or up to five input fields are displayed (dhmsf = days, hours, minutes, seconds and fracrion of seconds). If the format parameter is not used and as a default setting, all input fields are displayed.
And since I'm comletely unaware of Cargo and Semantic Mediawiki, I could not regard the needs of these extensions.
I would like to provide you with the outcome of my saturday programming workout :-) Is the email address from the Page Forms infobox still valid?--Wgkderdicke (talk) 15:35, 21 July 2018 (UTC)Reply
You've got mail. Since I discovered that you mentioned your email address a few topics above, I assumed that this address is valid. In addition to my saturday programming workout I added some checking for a mandatory duration field and some checking for the input values. Both is located in the PageForms.js file from the libs folder. Furthermore the input fields are providing some information as a tooltip. By hovering the mouse above a field a short abbrevation of the field name and the allowed range for this field is shown.
If you like this duration input, please feel free to integrate it into the Page Forms extension. In this case I will add the description to the input types page.
If I missed something or something is very awkwardly solved, please let me know.--Wgkderdicke (talk) 16:07, 22 July 2018 (UTC)Reply

Make Dynamic search with external data and mysql

Hi, I use external data to create a table in my wiki page using a select in a mysql database. I would like to make this select dynamic by passing a parameter. In my wiki page I would like to have a search box and then use the input text in my select. Is It possibile? And how? Thanks Natsuko79 (talk) 19:29, 19 October 2018 (UTC)Reply

The only way I can think to do it is with a Page Forms query form - see here. Yaron Koren (talk) 20:43, 22 October 2018 (UTC)Reply

open unlimited images

On Referata? I don't think that's a good idea. Yaron Koren (talk) 15:30, 26 October 2018 (UTC)Reply

Vandalism on Referata

Hi Yaron, I saw that there is some vandalism on Referata, and I cannot do anything without Admin rights (two accounts involved), is it possible to check on it please? Thank you very much. --LIMAFOX76 (talk) 08:59, 10 December 2018 (UTC)Reply