When adding a new item to a ''multiple-form'' dates from input type=patepicker are not stored in the first attempt. User has to go back to the form and reenter the date to the existing items. When entering more then one item in one edit none of the dates is stored in first attempt.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Fix handling of date(time)picker in new template instances | Yaron Koren | mediawiki/extensions/PageForms | master | +5 -0 |
Event Timeline
Comment Actions
I don't understand this. What's the difference between the first attempt and the second attempt?
Comment Actions
Okay, but why does it work for the second attempt and not the first? Is something being done differently the second time?
Comment Actions
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.
Comment Actions
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?
By the way, I should have asked before: what version of Page Forms are you running?
Comment Actions
No, this just hapens in '''multiple''' Forms while creating new items. I have not seen this while creating new pages generally. I can check this.
- CHECKED: This problem does not occur while creating new pages by simple forms.
By the way, I should have asked before: what version of Page Forms are you running?
PageForms 5.0
Comment Actions
Change 663066 had a related patch set uploaded (by Yaron Koren; owner: Yaron Koren):
[mediawiki/extensions/PageForms@master] Fix handling of date(time)picker in new template instances
Comment Actions
Change 663066 merged by jenkins-bot:
[mediawiki/extensions/PageForms@master] Fix handling of date(time)picker in new template instances
Comment Actions
Okay, I was able to reproduce the problem. Sorry about that! Hopefully this is the last of the new datepicker-related issues. I just checked in what I think is a fix for this.