June 12, 2014 at 5:34 pm #278121
We’re trying to build custom templates in the Template Builder, however we keep having an error time out occuring, stopping us from being able to generate new templates. Since we are creating variations of templates that already exist, is there a work-around solution we can go through on that back end perhaps? I have already tried disabling a few plugins to help the response time speed up.
The issue is usually along the lines of ” Fatal error: Maximum execution time of 120 seconds exceeded in /public_html/wp-includes/post.php on line 1999″
we’ve also had
“Fatal error: Maximum execution time of 120 seconds exceeded in /public_html/wp-includes/cache.php on line 455
Warning: reset() expects parameter 1 to be array, boolean given in /public_html/wp-includes/plugin.php on line 465
Warning: reset() expects parameter 1 to be array, boolean given in /public_html/wp-includes/plugin.php on line 465″
Thank you for your help!
June 12, 2014 at 5:55 pm #278129
- This topic was modified 11 months, 3 weeks ago by broadwaysbestshows.
Try increasing the maximum execution time:
Put this line of code in the wp-config.php file:
JosueJune 12, 2014 at 10:10 pm #278307
unfortunately this isn’t working… i’ve tried it multiple times, including increasing the value above 300. in additional, this is now appearing as a line at the very top of our site on the front end.June 13, 2014 at 8:49 am #278512
Did you try to deactivate all plugins – i.e. a cache plugin (cache.php) seems to trigger these errors too.
PeterJune 16, 2014 at 5:07 pm #279556
Hey, yes I have tried de-activating almost every plugin we use. I’m hesitant to deactive one or two of them as we had a developer go in and work some custom coding to make them work accurately. Today i was able to get the template builder to open and allow me to enter the name for a new template, however trying to make one results in an error occuring, and none of our already-existing templates appear on the left hand side.
AndyJune 16, 2014 at 7:14 pm #279643
You must be logged in to reply to this topic.