Publishing Error in WP 2.0.6

  • jdquel

    (@jdquel)


    19 years, 3 months ago

    I just recently upgraded to wordpress 2.0.6 and everything is running fine, accept that when I go to publish a new post or edit an existing one, I get an error message instead of being redirected to the manage posts page. The changes show up correctly on the public side of the blog and in the post management section of the UI, but still I’m getting this error message whenever I push the “publish” or “save” buttons on the post writing page.

    Does anyone know what this means?

    Warning: weblog_ping(/home/john98/public_html/wp-includes/class-IXR.php): failed to open stream: No such file or directory in /home/john98/public_html/wp-includes/functions.php on line 880

    Warning: weblog_ping(): Failed opening ‘/home/john98/public_html/wp-includes/class-IXR.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/john98/public_html/wp-includes/functions.php on line 880

    Fatal error: Cannot instantiate non-existent class: ixr_client in /home/john98/public_html/wp-includes/functions.php on line 883

Viewing 4 replies - 1 through 4 (of 4 total)
  • Les Bessant

    (@lesbessant)

    19 years, 3 months ago

    Sounds like this problem: http://wordpress.org/support/topic/54794?replies=3

    It’s possible that when you uploaded the new version, class-IXR.php was renamed to class-ixr.php. And that difference will cause the error.

    Check the name with your FTP program, and rename it if necessary.

    Thread Starter jdquel

    (@jdquel)

    19 years, 3 months ago

    Exactly… Turns out this was also a case sensitivity issue. To fix the problem, I just changed wp-includes/class-ixr.php to “wp-includes/class-IXR.php” My FTP client is set to change all file names to lowercase on upload, so that was probably the source of the problem for me.

    Thanks for pointing me in the right direction on that!

    DianeV

    (@dianev)

    19 years, 3 months ago

    That setting for an FTP client is problematic (it sounds better than it is) because file names should be *precisely* what they are … no automated changes!

    Thread Starter jdquel

    (@jdquel)

    19 years, 3 months ago

    I have my FTP client set to do that because it makes uploading images much easier to do and I haven’t had a problem with it until now. But yeah, I’ll definately have to turn that off next time I have to update wordpress or manage other more precise files like that.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Publishing Error in WP 2.0.6’ is closed to new replies.