[wp-trac] Re: [WordPress Trac] #4303: Fatal error: Maximum
execution time of 35 seconds exceeded
WordPress Trac
wp-trac at lists.automattic.com
Mon May 21 09:48:38 GMT 2007
#4303: Fatal error: Maximum execution time of 35 seconds exceeded
----------------------------+-----------------------------------------------
Reporter: tandilboy | Owner: anonymous
Type: defect | Status: new
Priority: high | Milestone: 2.2.1
Component: Administration | Version: 2.2
Severity: major | Resolution:
Keywords: |
----------------------------+-----------------------------------------------
Comment (by DD32):
Unfortunatly its a PHP setting which defines how long a PHP script can
execute. In your case it seems to be set to 35 seconds.
I'm assuming that when you mark a comment as spam, it calls home to
akismet HQ to add it as a spam comment in the database. Perhaps the host
which the WordPress install is installed on has a Slow downlink capacity..
Possible option:[[BR]]
use wp-cron to do the XML-RPC calls back home instead of doing it in
realtime when mark as spam is clicked..
--
Ticket URL: <http://trac.wordpress.org/ticket/4303#comment:1>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list