Skip Navigation

[Resolved] Unable to edit loop template for archives page – page request times out

This thread is resolved. Here is a description of the problem and solution.

Problem:

I get some PHP error:

Fatal error: Maximum execution time of 180 seconds exceeded

Solution:

please check these in your website:

In case it is a compatibility problem, please deactivate all other plugins, and switch to wordpress default theme 2019, deactivate all custom PHP/JS code snippets, and test again

Relevant Documentation:

This support ticket is created 5 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 5.96 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 17 replies, has 2 voices.

Last updated by danW-3 5 years, 4 months ago.

Assisted by: Luo Yang.

Author
Posts
#1284785

I have ruled out:
Companion Auto Updater
Media Library Assistant
UpdraftPlus
Wordpress Importer
WP Custom Admin Interface
Yoast SEO

These were least likely to be affecting it anyway.

#1284811

I disabled all plugins except Gutenberg and Toolset Blocks, Maps, Types and Views.

This time got an error screen:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in C:\Inetpub\vhosts\woolloff.com\staging.woolloff.com\wp-includes\l10n.php on line 1196

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0

#1284899

My issue is resolved now. Thank you! I decided to produce a reduced test case and discovered that somehow a theme I had tested out originally had installed the gutenberg development plugin without informing me. Disabling that and simply using the core version completely resolved the issue. So, something to be aware of, Gutenberg version 6.0.0 is not compatible with the current version of Toolset plugins.