WordPress.org

Ready to get started?Download WordPress

Forums

WP2.0.1: class-IXR.php Maximum execution time of 30 seconds exceeded (13 posts)

  1. Michael_
    Member
    Posted 8 years ago #

    When saving a new or existing post, I am getting the following error message after 30 seconds:

    Fatal error: Maximum execution time of 30 seconds exceeded in (...)\wp-includes\class-IXR.php on line 513

    Fatal error: Maximum execution time of 30 seconds exceeded in (...)\wp-settings.php on line 219

    This error occurs since I have updated from WP 2.0 to 2.0.1.
    An example of such post where this error occurs is here.

    I have already searched for this error message on the www, but did not find something useful. Ok, this blogger seems having the same problem like me.

    Any help is appreciated.

    Thanks,
    Michael

  2. shimmer1600
    Member
    Posted 8 years ago #

    Hi ! I got the exact same message. Almost everytime I send a new post, I get this message, but when I check the blog I realize that the message got posted anyway.

    Fatal error: Maximum execution time of 30 seconds exceeded in
    \wp-includes\class-IXR.php
    on line 513

  3. Michael_
    Member
    Posted 8 years ago #

    Anyone can help?

    Line 513 of class-IXR.php is
    $line = fgets($fp, 4096);

    This error occurs if I have a weblink like http://www.google.com in the post and if http://rpc.pingomatic.com/ is entered in the Update Services in WP Admin and if pings are enabled.

    So it seems being a pingback issue?

  4. Mark (podz)
    Support Maven
    Posted 8 years ago #

    Try removing the pingomatic link ?

  5. Michael_
    Member
    Posted 8 years ago #

    Yes, but when doing so, PingPack won't work anymore :-(

  6. Mark (podz)
    Support Maven
    Posted 8 years ago #

    http://codex.wordpress.org/Update_Services
    There are others until pingomatic is back.

  7. Michael_
    Member
    Posted 8 years ago #

    Thanks podz.
    But I wonder why not more bloggers are complaining about this error message since pingomatic seems to work. If I save a post the 2nd or 3rd time, it does work mostly.
    Also, IMHO the error message should be improved if the pingback service fails, '...maximum execution time exceeded...' is IMHO not sufficient.

  8. Mark (podz)
    Support Maven
    Posted 8 years ago #

    The error seems sporadic, and error messages I would agree on but then the coders will hope we don't see that :)

    The pingomatic issue has been raised though.

  9. Michael_
    Member
    Posted 8 years ago #

    Okay, thanks, didn't know that this pingomatic thing is a known issue. It was working like a charm on WP2.0, so I assumed it was caused due to my upgrade from WP 2.0 to 2.0.1.

    Michael

  10. rwgraeber
    Member
    Posted 8 years ago #

    Also getting this error -- for the record. Will remove pingomatic reference.

  11. Konquest
    Member
    Posted 8 years ago #

    Same thing here, but it only happened on my site hosted on a windows machine (IIS) and not on my apache server. I don't know if it could be linked though.

    I removed the pingomatic call and everything works well right now!

  12. FlyWEB
    Member
    Posted 8 years ago #

    Guys...found it! A workaround that is. Mind you I am not a programmer, just a simple seek and ye shall find person. One that is lucky to find this guy...a (former?) WordPress PHP programmer who knows what he is talking about I guess. No offence intended :)! By the way I am experiencing the very same errors while posting and seeing a WSOD regularly. Read all about workarounds and analysis at Owen Winkler's blog Asymtomatic. I for one am going to try his suggestions anyway. See what is does.

  13. FlyWEB
    Member
    Posted 8 years ago #

    Aah yes and the WP-trac patch that was published if you're interested. Don't know what it means but will give it aa whirl.

Topic Closed

This topic has been closed to new replies.

About this Topic