This thread is resolved. Here is a description of the problem and solution.
Problem:
After updating the theme Beaver Builder to the last version the home page started having a time out error:
Fatal error: Maximum execution time of 90 seconds exceeded in /wp-content/plugins/toolset-blocks/embedded/inc/wpv-filter-embedded.php on line 91
Solution:
Upon further review, our 2nd tier support team was able to find a fix for this issue.
If you have this issue, please try to follow the steps in the live site and check if it gets the issue fixed:
- Go to Toolset > Views
- Edit the problematic view
- Add suppress_filters="true" to the [wpv-post-body] shortcode in the loop(please check the screenshot bellow)
- Test to see if the error is fixed
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.
Hi, when I update Beaver Builder the site is crashing and the error coming is:
-----
Fatal error: Maximum execution time of 90 seconds exceeded in /home/gotland2/test.gotlandsmuseum.se/wp-content/plugins/toolset-blocks/embedded/inc/wpv-filter-embedded.php on line 91
-----
Let me set a private reply to get access to the test server.
We may need to take a copy of the site to investigate the issue further, but let's take a look first.
Can you clarify the action you take which generates this error?
You said "when I update Beaver Builder"; do you mean you are simply updating the Beaver Builder plugin?
If that is the case then I'd suggest you might just want to temporarily disable the Blocks plugin while you update Beaver Builder, and then re-activate Blocks.
But perhaps you mean the error occurs when you update a page made with Beaver Builder?
I checked it and the error only happens if all three plugins are enabled together Beaver Builder, Toolset Blocks and Events Calendar. Disabling any of the three causes the home page to load.
We tried enabling the debug mode to see if it gives us a hint on what's causing this issue but we don't have FTP access and we couldn't edit the staging site wp-config.php using a file manager.
Can you edit the wp-config.php of the test site and replace this:
define( 'WP_DEBUG', true );
with this:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
In addition to that, please see if it is possible to retrieve and share with us the HTTP error logs of today.
Thank you for making that change to the wp-config.php file.
I'd like to ask permission to make a new copy/staging version of your site where I can debug this in a different environment. Testing on a different setup is part of the troubleshooting and should give me more tools to debug this.
I'll make sure to delete this copy as soon as we get this issue fixed.
I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.
I will get back to you as soon as I get an answer from them.
I checked it but I'm afraid our 2nd tier support team is still debugging this issue.
In the mean time if you could reach out to Beaver Builder and check if they can look into this issue as well, we might be able to get to a solution faster with the two team involved in the debugging process.
It looks like there's a view 'Slider evenemang' that is built using Beaver Builder, if we click on the option 'Stop using Beaver Builder for this Content Template' the home page start loading again but without the layout. If we try to browse this view with the Beaver Builder managing the template we see this error message: 'wpv-post-body is being called inside itself creating an infinite loop', so it looks like something in the update might have changed causing 'wpv-post-body' to be call twice now.
We're actively investigating it and we'll keep you informed of our progress.
Upon further review, our 2nd tier support team was able to find a fix for this issue.
Please try to follow the steps in the live site and check if it gets the issue fixed:
- Go to Toolset > Views
- Edit the view Slider evenemang
- Add suppress_filters="true" to the [wpv-post-body] shortcode in the loop(please check the screenshot)
I tested it on the staging site and the issue is fixed in there.