- Issue created by @cbrowndc
Content users have created a set of events each month. They have used quick node clone to copy one set of events and then edited from there. They are finding the event's date fields are sometimes linked, meaning that the new event will edit the previous event's date field.
I couldn't reproduce on our dev site, but I checked the error report and there are unique nodes which will edit other unique nodes date fields. The events are event series for the month, which one event on a day of the week, but the cloned content is not part of the event series.
The relationship is in either directions as if the node's date field has both calling the same database field.
I will attempt to establish steps to reproduce.
Example
September Event(node id 20501) Date is Sep 3 12:00 -> November event (node id 20523) is edited to be November 5th 12:00 -> September Event(node id 20501) will now be November 5th 12:00 with no editing on that node.
Has any error like been reported previously? Am I misunderstanding how the module works? When I test against simpler events I see no linkage between node date fields.
Active
1.15
User interface