Hello Tribe,
The ECP changelog states “Changed how recurring events are stored, to give a unique post ID to each recurrence”. Does this imply that during an upgrade, existing recurring events will be refactored as individual events? Or will the new behaviour only apply to new recurring events that are created after the upgrade?
Just wondering because my preference would be a total refactoring of existing recurring events.
Our work on the recurring events will not break any of your existing recurring event series, and any recurring events that you make should continue to function in the same way. The changes we made are in the background, to lay the groundwork for some new features like more flexible recurring events, and ticketing for recurring events. Does that answer your question?
Best,
Leah
Author
Posts
Viewing 2 posts - 1 through 2 (of 2 total)
The topic ‘ECP 3.5 upgrade behaviour’ is closed to new replies.