Support » Fixing WordPress » php error when saving edits

  • TigerDE2

    (@tigerde2)


    Hi!
    I get the following when I try to save/publish any edits I made:

    Warning: fsockopen(): php_hostconnect: connect failed in /home/www/kunden/...path.../wp-includes/functions.php on line 1368
    Warning: fsockopen(): unable to connect to geourl.org:80 in /home/www/kunden/...path.../wp-includes/functions.php on line 1368
    Warning: Cannot modify header information - headers already sent by (output started at /home/www/kunden/...path.../wp-includes/functions.php:1368) in /home/www/kunden/...path.../wp-admin/post.php on line 368

    Edits are saved, however.
    What’s wrong?
    I’m using WP 1.0.1 RC1.
    (That’s at least what WP tells me…)
    Christian
    P.S.: The error occured first when I made my edited my last post this evening. Before, everything was working just fine…
    PP.SS.: HELP! 😉

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hmmmm, not just your error.
    I just edited a post – to see if this happened – and it did.
    My error:
    Warning: fsockopen(): unable to connect to geourl.org:80 in /home/—-path—-/wp-includes/functions.php on line 1368
    Warning: Cannot modify header information – headers already sent by (output started at /home/—-path—-/wp-includes/functions.php:1368) in /home/—-path—-/wp-admin/post.php on line 368

    TigerDE2

    (@tigerde2)

    hmm…
    looks as if geourl.org would cause the troubles.
    It’s probably down.
    It’s still uncool that it nearly crashes wp, though…
    Christian

    I just tried this morning, and it all works fine, so my guess, and it’s just that, is that the program times out after a while if the connection is not made. Not brilliant, but then at least it doesn’t just sit there waiting.

    TigerDE2

    (@tigerde2)

    well, yes, but I guess it wouldn’t be that difficult to return a custom error message instead of those php errors, and go on as usuall, instead of not printing the edit page…
    Christian

    Moderator Matt Mullenweg

    (@matt)

    Submit the code.

    This thread is several month’s old, but I just got that same error today (WP 1.2).

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.