Support

August 5, 2019 at 4:49 am

Hi Bill,

Normally the location of the error is important and in your case that’s:

An error of type E_ERROR was caused in line 210 of the file /wp-content/plugins/event-espresso-core-reg/core/services/collections/Collection.php

However, when the error is this:

Error message: Maximum execution time of 30 seconds exceeded.

The location gets a little hazy.

That error is basically saying ‘The script failed to finish what it was doing before the 30-second limit set on the server, so we killed the script’.

Could this be an issue with EE? Sure, it’s possible. But there are many other factors that come into play with this. For example, if there’s a whole bunch of logic running before EE loads that use up say 20 seconds, then EE starts to load its files/logic and 10 seconds later the limit it hit, its EE that shows the error, but the logic that chewed through most of the execution time.

The content should all be loading in much shorter times than that but it gives an example.

So having said that, we can troubleshoot this a little further.

Does this happen when you create a ‘new’ event? (Event Espresso -> Events -> Create new)

When you do get the above error, does the event in question have many datetimes/tickets?

Side note (somewhat related), your site is currently running on PHP version 5.6 which is now actually end-of-life, see: https://www.php.net/supported-versions.php

Have you considered updating the server to use PHP7? It is probably that biggest improvement you can make in terms of speed/performance without much effort. Meaning updating to PHP7 may ‘fix’ the above in that the code that previously took this long to run now runs much quicker and finishes within the time limit.

It is possible to increase the PHP max_execution_time to allow for the scripts to finish, but generally, they should be finishing within the default 30 second timeframe already.