WordPress.org

Make WordPress Core

Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#4303 closed defect (bug) (invalid)

Fatal error: Maximum execution time of 35 seconds exceeded

Reported by: tandilboy Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.2
Component: Administration Keywords:
Focuses: Cc:
PR Number:

Description

When i mark more than 5 comments as spam. wordpres shows the php error:

Fatal error: Maximum execution time of 35 seconds exceeded in /www/netherworld.com.ar/htdocs/radiotandil/wp-includes/functions.php on line 599

i using PHP version: 5.0.4 mySQL version: 5.0.22-max

Change History (7)

#1 @DD32
13 years ago

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:
use wp-cron to do the XML-RPC calls back home instead of doing it in realtime when mark as spam is clicked..

#2 @tandilboy
13 years ago

i not using akismet.

#3 @foolswisdom
13 years ago

  • Milestone changed from 2.2.1 to 2.4
  • Priority changed from high to normal
  • Severity changed from major to normal

#4 @markjaquith
13 years ago

If you're not using Akismet, then you're timing out when you're only updating 5 comments and up to 5 posts (to update their comment counts). That shouldn't be taking 35 seconds.

Is this a persistent problem? Is the site slow in general, especially when saving posts? Could just be that you server is very slow.

#5 @tandilboy
13 years ago

the site is not slow. just five comments take more than 35 seconds.

NOTE: i using 40 spam words in Comments Word Blacklist

#6 @ninjaWR
12 years ago

  • Resolution set to invalid
  • Status changed from new to closed

toss up between invalid and wontfix: seems to be a server issue to me

#7 @Nazgul
12 years ago

  • Milestone 2.5 deleted
Note: See TracTickets for help on using tickets.