Weblog ping component
Ping 1.0.0 is a component for pinging xml-rpc updating services (such as rpc.weblogs.com or rpc.technorati.com). To ping just select “Component - Ping - Ping” at the backend. You can edit list of rpc servers which to ping.
Downloads:
ZIP: com_ping.zip (TARGZ: com_ping.tar.gz)
This entry was posted
on Sunday, September 16th, 2007 at 6:20 pm and is filed under Weblog Ping, Extensions, Joomla!, SEO. You can follow any responses to this entry through the 
RSS 2.0 feed.
You can skip to the end and leave a response. Pinging is currently not allowed.
September 18th, 2007 at 1:06 am
Redownload Zip archive if you have an error [”PCLZIP_ERR_BAD_FORMAT (-10)”] installing it.
September 18th, 2007 at 1:09 am
Hello!
Interesting component. What section/category does it send? I ran a quick test, and it didn’t seem to give me any options on that. Does it just send everything in content?
Thanks!
Glen
September 18th, 2007 at 1:26 am
Glen Chancy:
It sends only “the fact” that site has been changed (so, it doesn’t send content itself).
This allows to various news and blogs search engines (e.g. technorati.com) faster update information about your site.
By the way, you can add
http://blogsearch.google.com/ping/RPC2
http://api.my.yahoo.com/RPC2
to servers list (Component - Ping - Servers) to more faster reindexing site by Google and Yahoo.
Read more in wikipedia.org.
September 18th, 2007 at 2:43 am
Thanks for this component, this is an excellent tool that finally enables Joomla to ping!
With some of the preset services, I get errors though. The message is almost always about having an “invalid (not well-formed) token at line 11, column 32, byte 151″.
I get this error (or a simpler error message) from ping.bloggers.jp, rpc.weblogs.com, ping.syndic8.com, rpc.technorati.com, and api.moreover.com.
blog.goo.ne.jp complains about a “not well-formed token on line 11, column 36, byte index 173, fault code -32700″.
services.newsgator.com said “HTTP/1.1 400 Cannot parse request”.
All other services accepted the ping.
Any chance you could look into this?
Thanks again, and kind regards,
Zorro
September 18th, 2007 at 7:09 am
Solved it myself!
I found out that line 11 of the sent data package comes from the variable $mosConfig_sitename. I have a German umlaut in my site’s name, that’s what made the ping services choke.
I put my site’s name inside the code in admin.ping.php, without the umlaut. Now the pings were all successful.
Many thanks again for an excellent component!
Kind regards,
Zorro
September 20th, 2007 at 12:39 pm
When I select “Component - Ping - Ping,” I get “Internet Explorer Cannot Display This Webpage.”
Am I doing something wrong?
September 20th, 2007 at 12:49 pm
Max:
Look at error log on your server. It may well be that component cannot connect to remote server because of your server restrictions.
September 20th, 2007 at 12:58 pm
How would I access those (sorry)?
And what would I do if that were the case?
September 20th, 2007 at 1:11 pm
Max:
You can usually find the errorlog in the control panel which gives by hoster.
If connection with other servers is forbidden, then there’s nothing to be done. But basically this problem appears on free hostings.
September 20th, 2007 at 7:33 pm
Hi There! This link is not Working