Dashboard>Options>Writing>Update Services

[cobwab]

Hey Steve et al.,

Your Services may not be current. These are the URLs that do pinging.

Go here in Dashboard (blog backend):

Dashboard>Options>Writing>Update Services

This is what's in mine:

http://api.feedster.com/ping
http://api.moreover.com/ping
http://blogsearch.google.com/ping/RPC2
cPanel®
http://rpc.technorati.com/rpc/ping
http://api.my.yahoo.com/rss/ping
Yahoo!
FeedBurner
http://ping.rootblog.com/rpc.php
http://ping.syndic8.com/xmlrpc.php
http://rcs.datashed.net/RPC2/
http://rpc.blogrolling.com/pinger
http://topicexchange.com/RPC2
http://ping.weblogalot.com/rpc.php
http://pingoat.com/goat/RPC2
http://rpc.blogbuzzmachine.com/RPC2
http://www.blogoole.com/ping/
Trend Tool - IceRocket
http://rpc.newsgator.com/
http://rpc.weblogs.com/rpc
http://www.bitacoles.net/ping.php
http://www.blogdigger.com/RPC2
http://ping.blogoon.net/ping/
http://www.blogroots.com/tb_popull.blog?id=1
http://www.blogsnow.com/ping
http://www.blogstreet.comxrbin/xmlrpc.cgi
Lasermemory.com - laser memory Resources and Information. This website is for sale!
http://www.newsisfree.com/RPCCloud
http://www.popdex.com/addsite.php
http://www.snipsnap.org/RPC2
http://www.wasalive.com/ping/
http://www.weblogues.com/RPC/
http://xping.pubsub.com/ping/
http://holycowdude.com/rpc/ping/
http://ping.weblogs.se/
http://blogmatcher.com/u.php
http://coreblog.org/ping/
http://www.blogpeople.net/servlet/weblogUpdates
http://bulkfeeds.net/rpc
http://trackback.bakeinu.jp/bakeping.php
http://ping.myblog.jp
http://ping.bitacoras.com
http://ping.bloggers.jp/rpc/
http://ping.blogmura.jp/rpc/
cPanel®
ishinao.net
http://bblog.com/ping.php
http://blog.goo.ne.jp/XMLRPC

So that everytime I post, it pings theses services.

Takes a while.

[golfer57]

Walt,
here are the errors from pinging off your list......
These are the lastest actions performed by the plugin.

02/10/08 18:35:53 - http://rpc.blogbuzzmachine.com/RPC2 could not be pinged. Error message: “transport error - could not open socket: 0 Success”
02/10/08 18:36:45 - http://www.blogoole.com/ping/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:45 - Trend Tool - IceRocket could not be pinged. Error message: “transport error - could not open socket: 0 Success”
02/10/08 18:36:45 - http://rpc.newsgator.com/ could not be pinged. Error message: “transport error - could not open socket: 0 Success”
02/10/08 18:36:45 - http://rpc.weblogs.com/rpc could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:45 - http://www.bitacoles.net/ping.php could not be pinged. Error message: “parse error. not well formed”
02/10/08 18:36:45 - http://www.blogdigger.com/RPC2 could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:47 - http://ping.blogoon.net/ping/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:47 - http://www.blogroots.com/tb_popull.blog?id=1 could not be pinged. Error message: “transport error - could not open socket: 111 Connection refused”
02/10/08 18:36:47 - http://www.blogsnow.com/ping could not be pinged. Error message: “parse error. not well formed”
02/10/08 18:36:47 - http://www.blogstreet.comxrbin/xmlrpc.cgi could not be pinged. Error message: “transport error - could not open socket: 0 Success”
02/10/08 18:36:47 - Lasermemory.com - laser memory Resources and Information. This website is for sale! could not be pinged. Error message: “transport error - could not open socket: 0 Success”
02/10/08 18:36:48 - http://www.newsisfree.com/RPCCloud could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:48 - WordPress › Error could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:49 - http://www.snipsnap.org/RPC2 could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:50 - http://www.wasalive.com/ping/ was successfully pinged (extended format)
02/10/08 18:36:50 - http://www.weblogues.com/RPC/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/10/08 18:36:50 - http://xping.pubsub.com/ping/ was successfully pinged (extended format)
02/10/08 18:36:50 - http://holycowdude.com/rpc/ping/ was successfully pinged (extended format)
02/10/08 18:36:50 - http://ping.weblogs.se/ could not be pinged. Error message: “transport error - could not open socket: 0 Success”

steve

[cobwab]

Thanks, Steve, I'll delete them from my blog.

[cobwab]

Hey,

I see that pingoat pings many sevices including technorati. Why don't we just use pingoat and none of the others?

[Kangaroo Jack]

Originally Posted by cobwab

Hey,

I see that pingoat pings many sevices including technorati. Why don't we just use pingoat and none of the others?

You can. The decision on what service you use is totally up to you.

[Boris_yo]

You can remove ping services and add every ping server to WordPress on your hosting so it will do the pinging.

Or you can use ping services (those that ping many servers) and let them do the whole job. Just make sure to remove any servers from your WordPress and leave ping services only.

Doing the second will ease the load on your hosting probably, i haven't tried it. And it will probably won't get your WordPress banned because of frequent pinging, since the ping services do the pinging and they are less likely to get banned.

[joaquin]

Thanks Cobwab.
I imlemented your updated Pinging List.
All Systems Go, We Have Lift Off

Joaquin