|
Sarah Schoeller
|
December 4, 2017 at 2:18 am
Hello
We recently upgraded our WordPress plugin Event Espresso to the latest version EE 4. Since the we’ve been experiencing timeout errors whenever we try to manually add a registration in the backend. Customers can also not complete event registrations as they’re getting the same error.
I’ve contacted our host who’ve advised me of the below:
I reviewed the case and noticed that the website is in general quite slow. Even before I submitted the login page for the Dashboard the following script took 30 seconds to complete:
Code:
http://www.thevillagemarkets.co/wp-content/plugins/s2member/s2member-o.php?ws_plugin__s2member_js_w_globals=1&qcABC=1&ver=170722-170722-657728950 → 30288 ms
After that I noticed that the database of the application was having quite the overhead for the *_options table (near 6MB could be reduced out of 15MB total size for this table) and needed to be optimized. Further more, the slow loading of this website prevented our internal caching service not being able to verify that the SG Optimizer is active, thus the SuperCacher service was actually not caching your website.
To help you resolve this, I have performed the following actions:
1. Optimized the database and reduced its size by using mysqlcheck. For this, you could use the phpMyAdmin tool:
https://www.siteground.com/kb/how_to_optimize_a_mysql_database_using_phpmyadmin/
2. Deleted old transients (temporary data usually created by plugins / theme) via WP CLI:
Code:
thevil15@sm17 [~/public_html]# wp transient delete –all
Success: 15015 transients deleted from the database.
3. Cleared old cached content and made sure that now the Dynamic Cache of SuperCacher is working.
4. Finally, I went ahead and enabled the Memcached level of caching of SuperCacher so that database calls made from the application would be cached as well.
AND
They’ve also supplied further errors.
Are you able to assist us with fixing this? Our site is at a halt because of this.
It’s urgent as we have bookings coming in tonight for an event.
Sarah
|
|
Josh
|
December 4, 2017 at 7:15 am
Hi Sarah,
We’ve received your request for priority support. I can review the slow queries that were logged and manually delete any errant options from the options that would affect the load time for Event Espresso.
I can also advise to deactivate the MailChimp add-on. I see that it’s activated, however, no API keys are set in the Event Espresso > MailChimp settings page. Any activated plugins that are not in use should be deactivated to help reduce the load on the web server.
|
|
Sarah Schoeller
|
December 6, 2017 at 2:58 am
Thank you. Do you need anything from me to do this?
I’ve deactivated the mail chimp plugin.
|
|
Josh
|
December 6, 2017 at 10:09 am
That’s already been done. Is your site still timing out?
|
|
Sarah Schoeller
|
December 6, 2017 at 7:05 pm
Yes, we I try to export the Filtered CSV report.
|
|
Josh
|
December 6, 2017 at 8:31 pm
That’s interesting, and a separate issue. I checked a few other items on the web server and the reason you see a timeout with the Filtered CSV report is because the following code is in the site’s wp-config.php file:
define( 'EE_USE_OLD_CSV_REPORT_CLASS', true );
I’ve commented out the above code and the timeout no longer happens, but there is a 403 forbidden error. You can contact your web host and ask them if it’s a file permissions issue or if they don’t allow long query string parameters. The Filtered CSV report uses long query string parameters and writes a temporary file to /wp-content/uploads/espresso/batch_temp_folder when it prepares the CSV report.
|
|
Sarah Schoeller
|
December 6, 2017 at 8:40 pm
Hello.
I had to add this code as neither export worked. I found it listed on the EEsupport forums after lengthy chats with our host, this was the best solution.
Any other suggestions?
|
|
Josh
|
December 6, 2017 at 9:02 pm
Not really. The server logs do not show why there’s a 403 forbidden error when the batch exporter tries to prepare the report. Your host may be able to narrow down why that’s happening. It’s likely a configuration issue because other Event Espresso sites hosted on Siteground do not have this issue.
If they cannot then I can suggest migrating to a new host. There is a list of recommended hosts here:
https://eventespresso.com/requirements/
|
|
Sarah Schoeller
|
December 12, 2017 at 1:46 am
Thanks. Siteground have asked what is the recommended PHP version for this plugin?
|
|
Josh
|
December 12, 2017 at 8:25 am
The recommended version is PHP 7.
|
