Extension talk:Page Forms

From MediaWiki.org
Jump to: navigation, search

Form input autofocus attribute[edit]

Is there a way to disable the 'autofocus' attribute from the text form inputs without manually hacking it out of the source code? I have issues on long forms where the autofocus shifts the page to the bottom of the form as soon as it is loaded because of that attribute (on pages using the #forminput parser functions). Removing it after the fact with jQuery doesn't work because by the time the jQuery call kicks in, the page has already been shifted down from the autofocus. --Lalquier (talk) 14:35, 4 April 2017 (UTC)

Nevermind - Answering my own question. I reviewed the list of parameters for #forminput and found I missed the 'noautofocus' parameter. --Lalquier (talk) 14:42, 4 April 2017 (UTC)

Pipes are not working with wikitable format[edit]

I get the following error when using a simple wikitable in a textarea box. Actual error message is "|" is not allowed, except within {{...}} or [[...]]

I see this was reported previously here: https://www.mediawiki.org/wiki/Extension_talk:Page_Forms/Archive_January_to_March_2016#Pipes_are_not_allowed

But it seems to be not working for us now. Version used: PageForms 4.0.2 (f0816ba) 22:12, 6 January 2017

MediaWiki 1.28.0 PHP 5.5.9-1ubuntu4.20 (apache2handler) MySQL 5.5.53-0ubuntu0.14.04.1

--Nischayn22 (talk) 07:29, 7 April 2017 (UTC)

A naked pipe will be interpreted as the end of the parameter you are trying to set with your field. Did you try transcluding the pipes with {{!}} ? - Lbillett (talk) 09:30, 7 April 2017 (UTC)

Nested Forms with Multiple Instances[edit]

I'd like to have a form that allows multiple instances and has an optional sub-form that can go with each instance. For example, you may have a main form (form "Item"), which can have an "Item Detail" sub-form. And you can have multiple "Item" instances, each with its own sub-form. Is this possible? I think this is what the partial forms are for, but I cannot figure out how to use it. Thanks in advance. Gstupp (talk) 20:12, 9 April 2017 (UTC)

Are you asking about having a form that only edits one instance of a multiple-instance template? If so, unfortunately that's not possible. Yaron Koren (talk) 22:41, 9 April 2017 (UTC)

Autocomplete not working[edit]

Can you think why autocomplete isn't working with the following?

{{#forminput:form=Contact|size=30|autocomplete on namespace=Contact|query string=namespace=Contact}}

I am sure it used to work, but I can't think what's changed. Thanks. Jonathan3 (talk) 14:15, 28 April 2017 (UTC)

Someone else said this was a problem too, but I can't reproduce it. Do you see any JavaScript error message in the browser console? Yaron Koren (talk) 17:35, 28 April 2017 (UTC)
Yes. This is from Firefox:
TypeError: this.source is not a function[Learn More]  load.php:6:984
        ._search http://www.mydomain.com/load.php:6:984
        $.widget/</prototype[prop]</< http://www.mydomain.com/load.php:78:450
        .search http://www.mydomain.com/load.php:6:853
        $.widget/</prototype[prop]</< http://www.mydomain.com/load.php:78:450
        ._searchTimeout/this.searching< http://www.mydomain.com/load.php:6:590
        handlerProxy http://www.mydomain.com/load.php:84:579
Jonathan3 (talk) 20:48, 28 April 2017 (UTC)
Could you add "?debug=true" (or "&debug=true") to the URL, to see if a more helpful error message can be seen? Yaron Koren (talk) 14:37, 30 April 2017 (UTC)
That didn't make any difference. It may be because I'm still using PF 4.1 (7f1cec5). I can't easily upgrade, as I haven't written that map/coordinates code for you yet, so have to add it each time... I'll get back to you when I do get the latest version. Jonathan3 (talk) 22:27, 1 May 2017 (UTC)
Ah - I'm pretty sure that upgrading will fix the problem, but until then, implementing these two changes directly in your code should hopefully fix the problem as well. Yaron Koren (talk) 01:58, 2 May 2017 (UTC)
I have reproduced the problem here, can you see it ? Nicolas NALLET Wiki-Valley.com, Semantiki.fr (talk) 09:40, 2 May 2017 (UTC)
This might be a different issue - in the JS console for that page, there's a Chameleon skin error that might be blocking the rest of the JS. Yaron Koren (talk) 13:36, 2 May 2017 (UTC)
Ok it's working now with Page forms version 4.1 (bb3327e) avril 27 2017 both here and vector skin based wikis. Thanks Yaron Nicolas NALLET Wiki-Valley.com, Semantiki.fr (talk) 07:04, 7 May 2017 (UTC)
The two changes mentioned above did the trick, thanks. Jonathan3 (talk) 01:27, 8 May 2017 (UTC)

Different list behaviour between dropdown and combobox[edit]

I have a property that has a set of allowed values defined using [[Allows value::xyz]]. If I put a field on a form related to this property, and I set the input type to dropdown, the dropdown list displays all the allowed values. In older Semantic Forms versions, the combobox input type also displayed the same list. Now, though, the combobox input type only lists the values that are actually assigned to the property on other pages. Is there any way to get the combo box to list all the allowed values? L Andy (talk) 15:57, 2 May 2017 (UTC)

Empty hidden field[edit]


I'm trying to use an empty hidden field like this:

{{{field|foo|default= |hidden}}}

I want the form to automatically add foo= to the template on the new page. But it does not seem to work, this parameter is not added to the new page.

Is there any way to do that?

--Rudloff (talk) 17:17, 5 May 2017 (UTC)

I don't know of any. Yaron Koren (talk) 01:44, 8 May 2017 (UTC)
I don't know why you would want to have an empty parameter, but off the cuff, have you tried wrapping nowiki tags around an empty value or space? Cavila 17:04, 8 May 2017 (UTC)

Issue with two datetimepickers in the same form[edit]

Hi, I have an issue when two datetimepickers are used in the same form. The datepicker-part is missing, but the time-part is shown. The problem disappears when I reduce to only one datetimepicker in the form.

Tested with both PF 4.1 and PF 4.1.1, MW 1.28.1 and SMW 2.5.1.

--BMfly (talk) 06:42, 11 May 2017 (UTC)

I can't reproduce this problem. What browser(s) are you using? And if you can get to see the JavaScript console, do you see any errors there? Yaron Koren (talk) 17:46, 11 May 2017 (UTC)
Tested with Chromium 58, Firefox 53 and Chrome 52, problem exists in all three browsers. Output from JS console:
This page is using the deprecated ResourceLoader module "jquery.effects.core".
This page is using the deprecated ResourceLoader module "jquery.ui.position".
This page is using the deprecated ResourceLoader module "jquery.ui.widget".
This page is using the deprecated ResourceLoader module "jquery.ui.core".
Please use "mediawiki.ui.button" or "oojs-ui" instead.
--BMfly (talk) 06:06, 12 May 2017 (UTC)
Those are all warnings that should be fixed (most of them come from Page Forms, I think), but I don't think any of them are preventing the JavaScript from running. This isn't on a public wiki by any chance, is it? Yaron Koren (talk) 14:13, 12 May 2017 (UTC)
I made a test on the sandbox SMW, which generates the same result: [1]. The form consists of two datetimepicker fields, but only the time picker part is visible. BMfly (talk) 18:07, 12 May 2017 (UTC)

editor=wikieditor does no longer work on 4.1.1 for "free text"[edit]

I just realized that after upgrading from Page Forms 4.1 to 4.1.1 the WikiEditor no longer shows up for the "free text", e.g. {{{standard input|free text|rows=25|autogrow|editor=wikieditor}}}. It continues to work for {{{field|description|input type=textarea|editor=wikieditor|rows=3|autogrow}}} but still I had to pull the new version. Cheers --[[kgh]] (talk) 19:47, 14 May 2017 (UTC)

There is a live example and the respective form definition is in this spot Cheers --[[kgh]] (talk) 07:29, 23 May 2017 (UTC)
Thanks for following up on this. I just checked in what I think is a fix. Yaron Koren (talk) 16:26, 23 May 2017 (UTC)

Is there a limit on number of values in a dropdown when populated from cargo fields?[edit]

I am trying to populate a dropdown (or combobox) using tokenized data stored as a single "List (,) of String" in a Cargo table.

The dropdown works - in that it populates, and I can select individual list items - but it looks like it's stopping at around 100 entries. Is this a limitation of values dependent on using Cargo, or is this a limitation with using a tokenized single list?

Here is the field declaration in the muti-instance template:

{{{field|ThirdParty|input type=combobox|cargo table=SOE_Versions_Store|cargo field=ThirdPartyCollect|}}}

The data is stored as {{#cargo_declare:_table=SOE_Versions_Store|ThirdPartyCollect=List (,) of String}} in a separate template.

Before I look to structuring the data differently (ie, store ThirdPartyCollect as separate rows instead of a delimited single entry), I'd like to know if this would solve the issue. FYI, the real goal is actually to combine several Cargo fields into a single, alphabetized dropdown in the spreadsheet-style view. I've almost got this in place, but it's konking out at 100 entries in the dropdown.

--Bgrenon (talk) 02:17, 16 May 2017 (UTC)

Is this happening in the spreadsheet display, or in a standard display? Or both? Yaron Koren (talk) 15:17, 16 May 2017 (UTC)

It looks like both. --Bgrenon (talk) 15:48, 16 May 2017 (UTC)

The fact that it's happening in the spreadsheet is not that surprising, but with the standard display it's quite surprising. What versions are you using of Page Forms and Cargo? Yaron Koren (talk) 17:49, 16 May 2017 (UTC)

Cargo 1.1.1 and Semantic Forms 3.7 --Bgrenon (talk) 18:19, 16 May 2017 (UTC)

Oh... those are both old, as I'm guessing you know. Maybe upgrading to the latest versions would fix the problem? Yaron Koren (talk) 18:31, 16 May 2017 (UTC)

Same settings, different resulting fields[edit]

I am not sure if it is a PF issue, but here we are: I have these two form fields:

{{{field|Has parent page|input type=tokens|values from concept=Institution|mapping property=Display title of}}}
{{{field|Has hierarchical superior|input type=tokens|values from concept=Instituton|mapping property=Display title of}}}

the only difference between the two is the name field. But when the form loads, it looks like different. See. We can see from the URL that both of the fields are sending the same information: Institution[Has hierarchical superior]=Configuração:Institution 003 & Institution[Has parent page]=Configuração:Institution 003

It seems like a bug. I am using PF 4.0.2 (fbecc9f). Jaider msg 20:28, 18 January 2017 (UTC)

That does look like a bug, yes. Yaron Koren (talk) 20:41, 18 January 2017 (UTC)
Cindy.cicalese maybe you have an interest in this bug. Jaider msg 13:53, 26 May 2017 (UTC)
That is indeed strange. Try removing the "|mapping property=Display title of", which is no longer necessary. You may need to update to a more recent version of Page Forms. Cindy.cicalese (talk) 14:16, 26 May 2017 (UTC)
Cindy.cicalese, done + errors:
  • Warning: asort() expects parameter 1 to be array, object given in /mw-REL1_28/extensions/PageForms/includes/PF_ValuesUtils.php on line 588
  • Warning: array_unique() expects parameter 1 to be array, object given in /mw-REL1_28/extensions/PageForms/includes/PF_ValuesUtils.php on line 589
    Jaider msg 14:30, 26 May 2017 (UTC)
(Just a brief note, to anyone reading this and confused - the first few lines, from January, were copied over from the archives.) Yaron Koren (talk) 16:21, 26 May 2017 (UTC)