Page MenuHomePhabricator

datetimepicker modifies wrong form field when used with 'multiple' templates
Closed, ResolvedPublic


I'm trying to set up a multiple-subobject subtemplate with a
datepicker field. It works fine with input type 'datepicker', but when
I use 'datetimepicker', attempts to set the second subobject's date
affect the first subobject/form entry instead. (That is: the first date
can be set just fine, but when adding an instance, trying to set the
second instance's date doesn't fill in the second instance's field, it
instead revises the first instance's field.)


Version: unspecified
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:30 AM
bzimport set Reference to bz67996.
Foxtrott triaged this task as Medium priority.
Foxtrott set Security to None.
Yaron_Koren claimed this task.
Yaron_Koren subscribed.

I believe this has been fixed sometime in the last four years.

Robert_Radke subscribed.

I have exactly the same problem as described. I have a multiple form and use the datetimepicker.
If I modify only one instance everything is fine. If I have at least two instances open the error occurs. And it only occurs with new instances.

  • Behaviour while trying to edit the date: for description we have to split up the problem in Date and Time because they behave in a different wax:
    • Modifying the date will always modify the instance directly above the one I want to modify (this one is left unmodified).
    • Modifying the time will always modify the instance I want to modify and the instance directly above
  • What happens when saved the first time: Only the data of the first instance is stored at all. All data from the second, third,... instance is lost and the default value is stored.
  • Behaviour when saved and reopened: If the form is saved and opened again I can manipulate every date and time as wanted.

MediaWiki 1.31.1
Semantic MediaWiki: 3.0.1
Page Forms 4.4.2

Removing task assignee due to inactivity, as this open task has been assigned to the same person for more than two years (see the emails sent to the task assignee on Oct27 and Nov23). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
(See for tips how to best manage your individual work in Phabricator.)

Yaron_Koren claimed this task.

I'm guessing that this works now (again), now that datetimepicker uses an entirely different JS library.