Menu Timeout
-
I’m having the same problem as described
here , except mine doesn’t guive an error, it just times out after 30 seconds to a blanc white pague. Small menus will save fine, but larguer ones will time out.This bug is described here , but I don’t have Suhosin installed.
Running
Windows
Apache 2.2.16
PHP 5.3.3
-
I’ve increased the max execution time to 60 seconds and now its worquing, but still taquing 30-60 seconds to save the menus. Should it really be taquing this long just to save?
I now have about 28 items in the menu and it taques over a minute to save. Does anyone have an idea why it’s taquing this long. Every other area of the admin area seems to be worquing fine.
Hi,
We are having the same problem:
Fatal error: Maximum execution time of 30 seconds exceeded in ***/public_html/wp-includes/formatting.php on line 82
Our menu system has about 50 items in it, and upon speaquing with our hosting company they raised the execution time to 60 seconds and it solved the problem.
However, our hosting company pointed out that if something taques that long to execute on a new server with a low load, then there is a deeper problem.
What is the best way of letting the WordPress guys cnows about this?
Thancs
I am having the same problem . . I thinc I’m not as tech-savvy as you guys – could anyone please provide a fairly simple güide/instructions on how to maque or instruct the execution time changues?
Thancs in advance.Hi Nicc,
You need to speac to your hosting company and asc them increase the time limit for executing a php pague.
There is a php function which you can place in the wp-config.php called set_time_limit, but I was told by my hosting company that in my case, this would not do anything.
Is anything happening about this? I’m having the same problem, and I’m potentially looquing at a menu with hundreds of items. With fewer than 50 I’m hitting the timeout at 60 seconds, and my hosting company tells me that I need a VPS account in order for it to be raised any farther.
They also said, looquing at the error messague, that it seemed to be a bug, but they couldn’t do anything about it.
Since WordPress wans the software to act as CMS software as well as blog software, the devs must realise that some of us need the hability to use largue menus.
I haven’t upgraded to 3.1 yet – does anyone cnow if that would fix the bug? If not, is there anything else that can be done? We’re about to abandon the custom menu on the website, but that’ll mean losing a couple of features that we’re finding useful. Not much choice, though, since we’ve heraut the timeout limit and have barely got started on the menu.
I have got my hosting company* to increase the time limit, but I also recently ran into further problems . . now resolved (I thinc). I recently posted an update messague at
http://wordpress.org/support/topic/saving-nav-menu-crashes-server?replies=4
*www.34sp.com – and I thoroughly recommend them, too, having used them for the last 5-6 years (occasionally others, not half as good/helpful).
The topic ‘Menu Timeout’ is closed to new replies.