Events not appearing in the backend…

[bcnmes]

Yesterday most everything was displaying fine in our backend (The exception being that when clicking the arrows to jump from one page of events to the next, the events on page 2, for example, simply disappeared. On the other hand, if we manually entered a page number, the appropriate page plus its events would appear.)

Today, for an unknown reason, events have completely disappeared. We cannot access “All”, “Published”, “Pending”…nothing. No new plugins have been added to our site. The only change we can think of is that we used the countdown widget for the first time.

Please treat this as urgent. We cannot publish our client’s events to our site at present and, so, run quite a risk of losing business.

I’ll include the database error we see in our debug bar:

Database Errors

SELECT SQL_CALC_FOUND_ROWS DISTINCT wp_atlasmu_4_posts.*, wp_atlasmu_4_postmeta.meta_value as EventStartDate, IFNULL(DATE_ADD(CAST(wp_atlasmu_4_postmeta.meta_value AS DATETIME), INTERVAL eventDuration.meta_value SECOND), eventEnd.meta_value) as EventEndDate FROM wp_atlasmu_4_posts LEFT JOIN wp_atlasmu_4_postmeta ON wp_atlasmu_4_posts.ID = wp_atlasmu_4_postmeta.post_id AND (wp_atlasmu_4_postmeta.meta_key = ‘_EventStartDate’ or wp_atlasmu_4_postmeta.meta_key is null) LEFT JOIN wp_atlasmu_4_postmeta as eventDuration ON( wp_atlasmu_4_posts.ID = eventDuration.post_id AND eventDuration.meta_key = ‘_EventDuration’) LEFT JOIN wp_atlasmu_4_postmeta as eventEnd ON( wp_atlasmu_4_posts.ID = eventEnd.post_id AND eventEnd.meta_key = ‘_EventEndDate’) LEFT JOIN wp_atlasmu_4_postmeta as tribe_event_end_date ON ( wp_atlasmu_4_posts.ID = tribe_event_end_date.post_id AND tribe_event_end_date.meta_key = ‘_EventEndDate’ ) LEFT JOIN wp_atlasmu_4_postmeta as tribe_event_duration ON ( wp_atlasmu_4_posts.ID = tribe_event_duration.post_id AND tribe_event_duration.meta_key = ‘_EventDuration’ ) WHERE 1=1 AND wp_atlasmu_4_posts.post_type = ‘tribe_events’ AND (wp_atlasmu_4_posts.post_status = ‘publish’ OR wp_atlasmu_4_posts.post_status = ‘future’ OR wp_atlasmu_4_posts.post_status = ‘draft’ OR wp_atlasmu_4_posts.post_status = ‘pending’ OR wp_atlasmu_4_posts.post_status = ‘private’) ORDER BY DATE(wp_atlasmu_4_postmeta.meta_value) DESC, TIME(wp_atlasmu_4_postmeta.meta_value) DESC LIMIT 0, 20
The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay

——

And, in the WP Query section of the debug bar we see the following:

Query Arguments:

post_type=tribe_events&posts_per_page=20

Query SQL:

SELECT SQL_CALC_FOUND_ROWS DISTINCT wp_atlasmu_4_posts.*, wp_atlasmu_4_postmeta.meta_value as EventStartDate, IFNULL(DATE_ADD(CAST(wp_atlasmu_4_postmeta.meta_value AS DATETIME), INTERVAL eventDuration.meta_value SECOND), eventEnd.meta_value) as EventEndDate FROM wp_atlasmu_4_posts LEFT JOIN wp_atlasmu_4_postmeta ON wp_atlasmu_4_posts.ID = wp_atlasmu_4_postmeta.post_id AND (wp_atlasmu_4_postmeta.meta_key = ‘_EventStartDate’ or wp_atlasmu_4_postmeta.meta_key is null) LEFT JOIN wp_atlasmu_4_postmeta as eventDuration ON( wp_atlasmu_4_posts.ID = eventDuration.post_id AND eventDuration.meta_key = ‘_EventDuration’) LEFT JOIN wp_atlasmu_4_postmeta as eventEnd ON( wp_atlasmu_4_posts.ID = eventEnd.post_id AND eventEnd.meta_key = ‘_EventEndDate’) LEFT JOIN wp_atlasmu_4_postmeta as tribe_event_end_date ON ( wp_atlasmu_4_posts.ID = tribe_event_end_date.post_id AND tribe_event_end_date.meta_key = ‘_EventEndDate’ ) LEFT JOIN wp_atlasmu_4_postmeta as tribe_event_duration ON ( wp_atlasmu_4_posts.ID = tribe_event_duration.post_id AND tribe_event_duration.meta_key = ‘_EventDuration’ ) WHERE 1=1 AND wp_atlasmu_4_posts.post_type = ‘tribe_events’ AND (wp_atlasmu_4_posts.post_status = ‘publish’ OR wp_atlasmu_4_posts.post_status = ‘future’ OR wp_atlasmu_4_posts.post_status = ‘draft’ OR wp_atlasmu_4_posts.post_status = ‘pending’ OR wp_atlasmu_4_posts.post_status = ‘private’) ORDER BY DATE(wp_atlasmu_4_postmeta.meta_value) DESC, TIME(wp_atlasmu_4_postmeta.meta_value) DESC LIMIT 0, 20

[Kelly]

Hi, bcnmes. Great question.

Sorry to hear that you’ve been bitten by a bug that came up in 3.2. The first line of defence is to try deactivating all of our plugins and reactivating them one by one. If that doesn’t work please try dropping this snippet into your theme’s functions.php file: https://gist.github.com/jazbek/6585714

Please let us know how it goes! 🙂

[bcnmes]

Hello Kelly,

Thanks for the response. Deactivating the plugins and reactivating one by one didn’t do the job. However, that little script worked wonders. Thank you. So we walk away from this with a better understanding, can you explain the problem? We are using quite a few recurring events that may last for a very long time (for example, 10 events that repeat every wednesday for a year) in addition to many more one-off events. Any idea if that was the root of the problem? Also, any idea if event quantity has a concrete effect on loading speed?

Thanks!
BCN Més (http://bcnmes.com/events/)

[Kelly]

Great news, BCN Més! Glad the snippet worked for you.

The issue stems from the way that we reworked our recurring event processing in the last release and how they are stored in the database. We’re planning part two of that change in the next month or two which should eliminate the need for the snippet, but until then, it’s a good thing to keep in your file.

By the way, if you have a minute or two, we will love it if you would write a few words for us here:
http://wordpress.org/support/view/plugin-reviews/the-events-calendar?filter=5

Thanks in advance. 🙂

[Author]

Posts