[ddel]

Is anyone still working on this? Three weeks and counting to sort a couple of pulldowns?

[ddel]

Confirmed fixed. Nice work, thanks. I have to admit I did not expect such a quick fix from you guys.

[ddel]

I’ve done some testing and can confirm that this bug is not related to the active theme or a conflict with another plugin. WP 4.8.1 with other plugins disabled, using one of the twenty* themes: events are visible in month view.

Update to 4.8.2 and events no longer show in month view. It’s likely related to the hardening of $wpdb->prepare() mentioned in the WP changelog.

[ddel]

Thanks for the followup but nope. Updated to 4.5.5 / 4.4.11.1 and there’s no improvement that I can see. The broken _EventRecurrence meta_value is unchanged after attempting to edit a broken recurring event.

Currently the client emails me when they need to work on a broken event and I fix the database for that event manually. Yay.

[ddel]

Hey András-

Thanks for the clear followup. At least knowing the actual cause is a positive. One quick question: If I manually remove the _EventRecurrence meta_key from the post’s postmeta, I can then re-create the recurrence rules and it seems as if that post is ok. Is this a viable long-term workaround while we await a fix?

In other words, if we were to do this for all of our broken events without completely deleting and recreating the entire event would that suffice or would the bad _EventRecurrence data issue return?

Another quick question: Do you guys post a full changelog somewhere? Trying to suss that information out of all of these separate release notes is a frustrating and time-wasting endeavor, especially given how slow the website often is.

[ddel]

Another piece of info. The _EventRecurrence postmeta metadata seems *really* screwy. I’ll attach that sucker here. If I delete _EventRecurrence for a post and then re-create the rules, I can then work with that post normally.

Can you tell me if this is indeed as screwy as it looks, and if so how something like this could happen?

Here’s the fixed recurrence data for post_id=2372:
a:3:{s:5:”rules”;a:1:{i:0;a:5:{s:4:”type”;s:6:”Custom”;s:6:”custom”;a:3:{s:8:”interval”;s:1:”1″;s:9:”same-time”;s:3:”yes”;s:4:”type”;s:5:”Daily”;}s:8:”end-type”;s:5:”Never”;s:14:”EventStartDate”;s:19:”2016-03-18 18:30:00″;s:12:”EventEndDate”;s:19:”2017-06-02 21:00:00″;}}s:10:”exclusions”;a:0:{}s:11:”description”;N;}

And attached is the fubar sql of post_id, _EventRecurrence for all of our recurring events.

You might ask the creator of https://theeventscalendar.com/support/forums/topic/script-error-freezes-in-firefox-when-editing-events/ if he’s seeing this behavior as well.

[ddel]

This reply is private.

[ddel]

Just updated to 4.5.3 and pro 4.4.9. No change, it’s still impossible to edit a recurring event due to script timeouts.

[Author]

Posts