By updating a series, it deletes all the eventinstances and recreates them, which deletes all information stored on the instance.

Ignore the last commit, I was getting 8.x-1.x in sync with 2.0.x

There are in the meantime newer issues that aim to implement different method of creating event instances.

Maybe now that the ground work is done we can close this issue and leave the implementation of different EventInstanceCreator plugins to followup issues?

It looks like the discussion that has been had here are now use cases that are solvable in dedicated issues.

• We can have an issue to make it possible to choose which plugin to use for an event series.
• A plugin that attempts to preserve event instances for as long as the start and end dates are unchanged: 📌 When changing recurrance, identical date combinations should not be deleted & recreated. Needs work
• A plugin that refuses to make any changes to existing event instances.
• A plugin that will move existing event instances to the nearest neighbor.

I am going to go ahead and close it, please feel free to reopen if you want to keep discussing possibilities here.

@pfrenssen Thanks for adding those. This is something I've run into with any recurring date feature, when you set up a bunch of event instances and want to be able to determine whether to keep existing ones and how to adjust them. I would really like to see something like an event management API that is also compatible with Smart Date and Recurring Dates Field.

Automatically closed - issue fixed for 2 weeks with no activity.