Extension talk:Page Forms/Known bugs and planned features

From mediawiki.org

Values dependent on and inline editing (jqGrid) would be really rock'n'roll.

--Planetenxin 16:59, 27 October 2011 (UTC)Reply[reply]

Editable-grid input for multiple-instance templates[edit]

I really look forward to this planned feature. And jqGrid seems to be a good choice to implement this.--Even Thorbergsen 14:47, 7 February 2012 (UTC)Reply[reply]

restricting auto-completion values[edit]

--EvgeniyDankovcev (talk) 23:52, 20 March 2013 (UTC) once your wiki gets huge a necessity raises up to restrict auto-completion list based on some criteria e.g. not display all the values from certain category (autocompletion on category) but filter only those which have certain value of specific propertyReply[reply]

Any Semantic Form in wiki results as UNIQ...QINU[edit]

Hi all,

I have configured semantic mediawiki, I am using semantic forms to record some information as I need. Yesterday my site was running ok but today any semantic form results something like:

UNIQd918e943ff996176-item-1--QINU? ?UNIQd918e943ff996176-item-2--QINU?

Regarding VisualEditor - 2015[edit]

Yaron, I mentioned your name in in TS50429... but not in vain, or at least I don't think so. Noted here in case there's an accuracy problem, and to let others chime in here to indicate whether it's important to them or not. --Salquint (talk) 16:44, 15 January 2015 (UTC)Reply[reply]

That does look accurate, and thanks. Yaron Koren (talk) 22:24, 15 January 2015 (UTC)Reply[reply]

What about Rename page parser function?[edit]

I will really appreciate a new function which permits to automatically rename a page when this page is mentionned in a form field which is renamed.

When do you think this function could be created? Maybe I could find some money to help this development.

I don't know how that would work... if a form field value changes from "A" to "B", how do you know if that's because A was renamed to B, or if it's just a new value for the page? You should check out the Replace Text extension, though - it's not what you are asking about, but it could be helpful. Yaron Koren (talk) 03:14, 24 April 2019 (UTC)Reply[reply]

Is there a way to do range sliders?[edit]

Using "mw-" tags while saving a form[edit]

Could we add all the tags ("mw-new-redirect", "mw-blank", and so on) listed in Special:Tags while saving a form, for instance by adding a parameter to {{{standard input|save|tag=mw-new-redirect}}}? --Manu.wikidebats (talk) 17:34, 11 March 2020 (UTC)Reply[reply]

Mobile version for forms[edit]

Is a mobile version for modifying forms planned? The "Save" button works, but the "Add new instance" does not. Thanks -- 17:54, 1 April 2020 (UTC)Reply[reply]

By "mobile", I assume you mean that it works with MobileFrontend, i.e. the Minerva Neue skin. I don't know how to get Page Forms' JavaScript to work with that extension/skin, but it would be great if it could be made to work. Yaron Koren (talk) 23:02, 1 April 2020 (UTC)Reply[reply]

Preloading data in an existing page[edit]

It is currently not possible to preload data in an existing page, as described here: "Note that this only applies to adding new data, or to query forms; for editing an existing page, there is no way to set the contents of the form to anything other than the current contents of that page."

@Yaron Koren: Would there be a way to change this? Would it be a hard job?

Thanks for your response. Manu.wikidebats (talk) 09:36, 31 March 2022 (UTC)Reply[reply]

It wouldn't be hard to do, but I don't think it's a good idea. Why should a form modify a page after it has already been created, without the user's consent or even awareness? I don't see a reason for it. Yaron Koren (talk) 15:32, 31 March 2022 (UTC)Reply[reply]

Thanks for your reply! By example, it could be a way to add a new instance in a multi-instance template in an existing page. In my case, that would be very useful. Manu.wikidebats (talk) 19:25, 2 April 2022 (UTC)Reply[reply]

Is the idea to add a new instance with pre-set field values? If so, maybe #autoedit is the better solution. Yaron Koren (talk) 13:28, 4 April 2022 (UTC)Reply[reply]
No, it needs to be added with a #forminput. Manu.wikidebats (talk) 09:37, 5 April 2022 (UTC)Reply[reply]
Why? Yaron Koren (talk) 12:36, 5 April 2022 (UTC)Reply[reply]
Because the page to edit will depend on what the user write in the #forminput. There is no predetermined target as needed for an #autoedit.
The idea is for the user to write the title of an argument, and for the template to add invisibly the page ID where the argument is used. If the argument is new, there is no problem; but if it still exists and we want to add another page ID where the argument is also used, that is actually impossible. Manu.wikidebats (talk) 15:15, 5 April 2022 (UTC)Reply[reply]
Here is an example. When the user enters an argument title and clicks on "Validate", the #forminput invisibly preloads the page ID where this argument will be used and the nature of the argument (PRO or CON). This ID and this nature will fill a hidden parameter of the argument form in which the user will add a summary, quotations, etc., of this argument.
If the entered argument still exists in the wiki, the ID and the PRO/CON nature of the argument could not be saved. This is the problem.
So my question is: how to make possible to preload data with a #formlink in an existing page (and not a new one)?
Thanks for your reply! Manu.wikidebats (talk) 12:34, 6 April 2022 (UTC)Reply[reply]