We see lots of long query errors in our logs. We also see lots of 502 Bad Gateway errors. I am not certain the two are related, but this is my suspicion. I think it may be the case that the long queries are bogging the server down, which makes it unable to serve pages\u2014thus the 502s. Interestingly, the 502s are not generally seen on the events page but on random pages on a subsite of our multisite network.<\/p>\n
We don’t have very many events. Maybe a few dozen, none recurring. Our site is hosted on WP Engine at the “Professional” tier. This should be more than enough to handle our traffic. <\/p>\n
I see that there are several threads related to issues with the Events Calendar on WP Engine hosted sites, however I haven’t been able to find any that give solutions. The closest I’ve seen is this thread from this July [https:\/\/tri.be\/support\/forums\/topic\/abandoning-events-calendar-pro\/], in which Caleb wrote that the issue could be resolved by removing the limit on WPEngine’s side:
\n========
\nThis is a known issue with WP Engine, since they limit the length of SQL queries. Try adding the following to your wp-config.php file, which should hopefully disable that limit in WP Engine:
\ndefine( ‘WPE_GOVERNOR’, false );
\n========
\nI asked WPEngine if I should do this, and they said that this would prevent the error from being logged but would not prevent the error itself. So I don’t think that will solve my issue.<\/p>\n
So far I’ve updated both Tribe calendar plugins, updated WordPress, deactivated and deleted Events Calendar Pro, and removed the plugin from a sub-site (blazingmountain.org). Still seeing the long query errors.<\/p>\n
So my main question is how do I get the plugin to stop generating these long query errors. My secondary question: Do you think the long query could be related to the 502 errors.<\/p>\n
I love the plugin! Please help me figure out how to make it work for my site. Thanks!<\/p>\n","protected":false},"template":"","class_list":["post-877508","topic","type-topic","status-closed","hentry"],"yoast_head":"\n