[Jackson Whelan]

Horrible news and sad way to handle an upgrade. Surely there was a better way. They have dozens and dozens of events and it’s an understaffed community organization that can barely afford a license for this plugin. Hope you can pay more attention to not breaking sites with future upgrades.

[Jackson Whelan]

This reply is private.

[Jackson Whelan]

You are correct the problem occurs with recurring events that were created some time ago.

I have confirmed the problem exists using default theme with no plugins other than TEC plugins.

How do we fix the older events?

It really seems like run away javascript gone wrong. Not finding anything in server logs.

[Jackson Whelan]

Flushing the permalinks did not fix it but what did was:

– Changing to default ?p=123 – update settings
– Checked a single instance, it worked
– Changed back to /%postname%/ – update settings

Thanks

[Jackson Whelan]

The reason usually seems to be that user made an error in data entry and does not realize it, and the combination of bad dates and a bad rule = thousands of events being created, which then times out when trying to delete them all, so you end up going into the database and running queries to clean up all the posts and attendant post meta.

So my suggestion would be a ‘Are you sure you want to do this?’ sanity check when the combination of dates and rules equals more than 100 events being created.

I think the common way this happens is they have a daily event and set the start and end date to equal the first and last occurrence, but instead it creates many copies of an event that lasts a month, etc.

[Author]

Posts