Unable to ping Ping-o-Matic

[macmanx]

When I post (with ping-o-matic in the update services), none of ping-o-matic's services are notified. However, If I post with all of ping-o-matic's services entered separately into the update services field (blo.gs, weblogs.com, technorati, etc.), they are successfully notified. And I have attempted as many troubleshooting steps as I know, including re-upgrading from the .tar.gz version (previously used the .zip version), using a different FTP app to upload the files, and testing trackbacks/pingbacks with all plugins deactivated and using the default theme. I'm out of ideas, and I'm pretty sure this is a WP bug as I had no problems with pinging ping-o-matic in WP v1.5.

I should also add that my server error logs are empty for today, and that I am having any issue with pingbacks (bug# 1324) which may be related.

If you would like it, my phpinfo file is available upon request via email to james at macmerc dot com.

[macmanx]

I tried another test post and can see (via ping-o-matic's 100 recent pings list) that I have successfully pinged ping-o-matic. But, none of the external services are showing that they have been updated as a result of the ping-o-matic ping. Perhaps this is a problem on ping-o-matic's end.

[macmanx]

Update: I'm having the same problems with a brand-new fresh WP v1.5.1 installation.

[macmanx]

Update: I had no problems with a fresh WP v1.5.0 installation. This appears to be a problem with WP v1.5.1.

[macmanx]

More info from my error logs:

[10-May-2005 10:43:30] PHP Warning: fclose(): supplied argument is not a valid stream resource in ///*/wordpress/xmlrpc.php on line 1189
[10-May-2005 10:43:30] PHP Warning: Cannot modify header information - headers already sent by (output started at ///*/wordpress/xmlrpc.php:1189) in ///*/wordpress/wp-includes/class-IXR.php on line 371
[10-May-2005 10:43:30] PHP Warning: Cannot modify header information - headers already sent by (output started at ///*/wordpress/xmlrpc.php:1189) in ///*/wordpress/wp-includes/class-IXR.php on line 372
[10-May-2005 10:43:30] PHP Warning: Cannot modify header information - headers already sent by (output started at ///*/wordpress/xmlrpc.php:1189) in ///*/wordpress/wp-includes/class-IXR.php on line 373
[10-May-2005 10:43:30] PHP Warning: Cannot modify header information - headers already sent by (output started at ///*/wordpress/xmlrpc.php:1189) in ///*/wordpress/wp-includes/class-IXR.php on line 374

The "headers already sent" errors appear to be caused by the "supplied argument is not a valid stream resource" error.

edited on: 05-10-05 18:31

[anonymousbugger]

What happens if you remove the 'fclose($fp);' on line 1189?
($fp is undefined, there's no matching fopen)

[macmanx]

Thanks for replying! Unfortunately, this is getting too confusing. A recent test with the unedited xmlrpc file did not work (as predicted) and produced no errors in error log (argh). A recent test the edited xmlrpc file (as per your instructions) also did not work, and also did not produce any errors in the error log.

[anonymousbugger]

This seems to be a bug in extended ping, but I don't know why it works on most sites but not on mine and macmanx's. In the weblog_ping function in functions.php I changed:

if ( !$client->query('weblogUpdates.extendedPing', get_settings('blogname'), $home, get_bloginfo('rss2_url') ) ) then try a normal ping

$client->query('weblogUpdates.ping', get_settings('blogname'), $home);

to just be:

$client->query('weblogUpdates.ping', get_settings('blogname'), $home);

so that it always does a normal ping. This made it work for me.

Of course, it could be that macmanx's problem is a different one than mine, but the symptons have been the same so far...

edited on: 05-11-05 06:07

[macmanx]

That works perfectly! Thank you, anonymousbugger2. Can you think of anything that would be negatively impacted by that edit?

edited on: 05-11-05 04:21

[anonymousbugger]

Heh, we're winding up with the same discussion on both the support forum and on here, but I guess I'll keep it up for anyone only following along at one place. :)

This isn't a real fix, it's just a workaround. Getting rid of that line makes it so WP never tries to use the new "extended ping" bit that was added in 1.5.1, which seems to have some bug that was making pings not work for us. It shouldn't be able to break anything else or have any other negative effects.

-- Herschel

[macmanx]

Herschel, you've done it! Your fix has worked perfectly so far.

[macmanx]

I did find one problem. Though all of ping-o-matic's external services receive the ping, ping-o-matic does not record your ping's visit in it's stats. ::sigh::