+1 for this feature.

The replacement of {{ and }} seems to be solved in V 1.3. I have not seen it currently. I replaced {{ by {{ and }} by }} with Extension:ReplaceText every time it occured.

Yup, in fact it works...

I gave V5.2.1 a chance and could not reproduce this issue. The counter must not be set to [0].

Ok, it works for me too. Thank you.

In T274154#6815277, @Yaron_Koren wrote:

Okay, so for you, the "datepicker" input saves its value to the page when editing an existing page, but not when creating a new page?

I think not. Just open the form, enter the date and save the page. The only difference I see is the already exisiting item on the second time.

On the second attempt the date is stored for existing items.

In T269355#6704998, @Yaron_Koren wrote:

I understand that you'd prefer having the button on a separate line, but can you live with the current approach? Could you just expand the width of that table cell/column?

I'd prefer the former design - the space around depends on the size of the input field. At this moment parameter size is pretty useless and the current behaviour makes #forminput unuseable in many existing cases. Example:

Well, I at least I'm not shure if datepicker used this format for saving data. I crawled thru my date data today and found that MM.YYYY format for a number individual values. Maybe these have been entered by the editor or text-fields.

Switching to input type= date does not solve the problem as it even does no longer fully handle incomplete dates. Example: https://sandbox.semantic-mediawiki.org/wiki/Peter_Parker . This depends on how the date is saved on the page sth. like January 2020 is OK but not 01.2020 . 01.2020 is the style that datepicker before saved the date on page in my wikis -> so all this dates get lost anyway.

This is for datepicker and datetimepicker. I just dubblechecked with V 4.9.5 : 4.9.5. did not touch the incomplete dates when the page is opened by form and it allows entering incomplete dates wich is a precondition.

No, I think it just display as the data was - 2020 in your case, because it did not change the values, when the page is opened and saved by form.

This happens, when there is an ''incomplete'' Date in the field , f.e. 2020 or 04/2019. It just clears the field when page is opened by form even the date flield it is not touched by the user.

For styling puposes. I like to have some explanation beside the forminput, because not everybody seem to understand how to use it (Mostly because people just click the button without entering something to the input flield).

In T269334#6667147, @Yaron_Koren wrote:

Sorry about that! I think this is fixed now.

I updated PageForms to 4.8 a minute ago and this error has gone. Thanks.

My wikis are on 4.6 at the moment. Maybe I try an Update the next days.

And, I quickly did a fresh install of 1.25.2 and it is still the same there. Seams nothing changed there for a while.

I quickly did a fresh install of 1.23.10 and it is still the same there.