After Deleting Recurring Event Instance, Editing 'All Future' Recreates Them

[Cliff]

I know how to delete individual instances in a recurring event (https://theeventscalendar.com/support/forums/topic/again-can-i-delete-individual-instances-of-a-recurring-event/) and that works fine. However, let’s say I do the following:

1. Create event recurring each week for the next four months.
2. Delete a few instances that fall on a holiday (all is well at this point).
3. Go back and change the price of the recurring event.
4. **All of the events I deleted are now back.**

I understand I’m essentially applying everything inside an event again when I update it, but there should be some way to track what’s already been deleted, or at least a prompt to ask me what I’d like to do, should there not? This is creating quite the hassle.

Any ideas? I’ve tried deleting in different ways, setting to draft/private, etc., and no dice.

[Joyce Grace]

Hello Cliff,

This is a very interesting issue and I will try to test it on my end. It may be a bug in our system.

To get us started with supporting this issue, can you confirm with me you’ve done all of the following?

Updated to the latest version of WordPress?

Updated to the latest versions of our plugins (2.0.8) and all our add-ons?

Try setting your permalinks to ‘postname’ in Settings > Permalinks?

Try refreshing your permalinks by visiting Settings > Permalinks (it does it automatically)?

Also, can you tell me which of our plugins and add-ons you have running on your site right now?

Thanks!

[Cliff]

Joyce,

All of that’s confirmed. The site’s running The Events Calendar and The Events Calendar Pro. Thanks!

[Andy Fragen]

Joyce, I can confirm the same behavior. I think what’s going on is that once a modification to a repeating event is performed, it will touch every event that fits into it’s repeating pattern. To counter this any variations in the repeating pattern, like deletions of individual events within that pattern, would have to be stored within the database so that a ‘Save to All Occurrences’ would specifically know when to skip.

[Joyce Grace]

Thank you so much Andy, and Clif!
I will bring this to the attention of our developers and see if we can get a fix to this, especially some help for Clif in the meantime.

[Cliff]

Thanks, Joyce. Anything would be great at this point. 🙂

[Cliff]

Any updates on this? I would prefer not to solve this myself as I know my solution won’t be as graceful or future-proof.

[Joyce Grace]

Hello Cliff,
Our team was discussing it today actually. I know it sounds quiet on our end, but in fact there is a lot of activity happening with these support requests on our back end. We get together often, communicate internally and things like this get brought up. So we are working on it! Chances are it may not be fixed in the next release, but we are having another developer look at it to see how it can be addressed.

Thanks for your patience!

[Author]

Posts