Unnecessary huge mysql request nearly crashes server

[Jens]

Hey there,

there is a (unnecessary) huge mysql request in your Calendar that chrashed our database several times in the past days.
We run a blog with about 80.000 posts and 50.000 media elements (pictures, etc.). Obviously, your Calendar (the widget maybe?) goes through each and every database entry (posts, pictures, users, tags, …) and sorts them before showing the top 5 (and deleting everything else afterwards). In our case, this causes the server to download the whole database to hd to perform this task, since the db is way too big to be processed in the memory. There is a query called databasename_posts.* which causes the main problem.

Unfortunately, we are not able to use this plugin anymore, until there is a fix for this issue.

[George]

Hey Jens,

Thanks for reaching out.

You say, “and sorts them before showing the top 5.” Can you show a screenshot (either on your site or on our demo site at wpshindig.com/events) or some other clarification of what specific widget made a list of the “top 5” events?

Thank you,
George

[Jens]

This reply is private.

[George]

This reply is private.

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts