Just upgraded to 3.10 and am getting timeout errors

[Anthony]

I am getting timeout errors when viewing the calendar. The errors do not all occur in the same section of PHP code.
Does anyone have any suggestions? Generally the errors are in Modern Tribe code but the one below is not.

Fatal error: Maximum execution time of 30 seconds exceeded in /home/content/g/a/n/gandtkellett/html/citymagazine/wp-includes/cache.php on line 111

[Barry]

Hi Anthony,

I visited your main events page and experienced almost exactly the same thing:

Fatal error: Maximum execution time of 30 seconds exceeded in /.../html/citymagazine/wp-includes/plugin.php on line 207

This definitely isn’t ideal and while it is possible to increase the timeout limit from 30 seconds to something higher like one minute, that in itself is not ideal.

I’m curious:

• Did this suddenly just start happening (if so, what if anything changed immediately before the problem started)?
• You indicated having run through our standard troubleshooting steps – ie, deactivating all other plugins and switching to a default, unmodified theme such as Twenty Fifteen – did that help with the problem?

Thanks!

[Anthony]

Thanks for the reply Barry. It started to happen immediately after I upgraded to 3.10. It never happened before and no more events had been added.

Where do I change the timeout? I would rather have the use wait a little longer that get the error message.

Deactivating the other plugins and an unmodified theme did not help.

Tony

[Barry]

Hi Tony,

That’s frustrating.

The steps for changing the timeout vary from host to host, so it may be best to check in with them – as, in some cases, it is not permitted to increase this (or you may need special permission). That said, here are some links offering up a little more information about PHP max execution time:

• PHP settings: max_execution_time
• Related post on wpbeginner.com

Does that help in the short term?

[Anthony]

Hi Barry,

Thanks for the information, I think I need to call my hosting provider (GoDaddy) as I do not seem to have access to the necessary files.

I noticed another topic from someone else on a significant slowdown on the Month view after the 3.10 update. That sounds like exactly the same issue I am having, the other views I have tried, List and Day, seem to be working. Month view works if I filter the events first, it fails consistently when I try to view all events.

Tony

[Barry]

Hi Tony,

That’s an interesting observation and in fact the team was just discussing those related reports. Would it be possible for you to confirm a few more things?

• Does Events Calendar PRO have a bearing on this? If you temporarily deactivate it, for instance, do you find month view finishes loading?
• Similarly, is there a link between Filter Bar and the slowdown that you can detect?
• My estimate is that you have somewhere in the region of 2,200 upcoming events – is that accurate? Roughly how many are there in total and what percentage approximately are recurring in nature?

For that last question, a count should be available in the admin event list screen.

It does also seem that even list view is loading rather slowly – the fact that it is limited to just 10 events might be part of the reason it is able to complete loading, as compared to month view where I’m guessing a great many more events would display if it finished loading.

Do you feel there has been a slowdown there, too, even if it doesn’t trigger timeouts – or is that pretty much loading at the same speed as it was pre-update?

Thanks again!

[Anthony]

Hi Barry,

I did try deactivating the Pro and Filter Bar plugins but it still gets the timeout. I am afraid I do not have any timing data but I feel the events are loading slower, even in the List view.

There are 3799 events. Estimating the number of recurring ones is difficult but I would estimate about 30% of them.
Is there a database table I could look at with something like ABase to get an accurate count?

Thanks

Tony

[Barry]

I think that’s fine, it gives me a good sense of the scale (and type) of events you are dealing with. Bear with me a little longer, I’m going to compare notes with some fellow team members and we’ll figure out a further course of action from there.

[Barry]

Hey Tony,

When I review your system information (that you shared when you opened this post) I see no reference to our new month view caching setting.

Can you visit Events → Settings → Display and check to see if Enable the Month View Cache has been checked and check it if it has not already been enabled (then save the changes)? That may not solve this immediately if the cache cannot be generated owing to the timeouts, but it could be worth a shot.

[Barry]

Hey again Tony,

We’re looking at this in a little more depth and wondered if you’d be comfortable sending us a database dump?

Lots of database tools such as phpMyAdmin will help you to do this (and alternatively something like the Duplicator plugin would give us a database dump as part of a bigger package – and is quite easy to use).

If you are open to doing this, would you be able to upload the resulting file to a suitable location (whether your WP site, Dropbox or some similar service) and share a download link by private reply?

Thanks!

[Anthony]

This reply is private.

[Barry]

Thanks Tony! We’ve now identified some issues that are likely to be contributing to this problem and are actively working on a fix.

[Anthony]

Thanks Barry.

I was just re-reading the thread and I noticed I did not reply to the suggestion about the Month View Cache. I did enable this at one point, probably after the initial post but, as you suspected, it does not make a difference.

[Barry]

That’s a shame – I guess the cache cannot be built due to the timeout so it’s potentially helpful effects will not be able to kick in.

We’ll do our best to update you here in this topic once our proposed performance fixes are released 🙂

[Anthony]

Barry,

Is there any news on this? It makes it very difficult to use the calendar with this problem. What are the options to revert to the earlier version until this is fixed?

Thanks,

Tony

[Author]

Posts