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)

Related Posts

41 Responses to “Weblog ping component”

  1. 1
    Physicist Says:

    Redownload Zip archive if you have an error [”PCLZIP_ERR_BAD_FORMAT (-10)”] installing it.

  2. 2
    Glen Chancy Says:

    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

  3. 3
    Physicist Says:

    Glen Chancy:

    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?

    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.

  4. 4
    Zorro Says:

    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

  5. 5
    Zorro Says:

    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

  6. 6
    Max Says:

    When I select “Component - Ping - Ping,” I get “Internet Explorer Cannot Display This Webpage.”
    Am I doing something wrong?

  7. 7
    Physicist Says:

    Max:
    Look at error log on your server. It may well be that component cannot connect to remote server because of your server restrictions.

  8. 8
    Max Says:

    How would I access those (sorry)?
    And what would I do if that were the case?

  9. 9
    Physicist Says:

    Max:

    How would I access those (sorry)?
    And what would I do if that were the case?

    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.

  10. 10
    Argetim Says:

    Hi There! This link is not Working

  11. 11
    Physicist Says:

    Argetim:

    Hi There! This link is not Working

    What link?

  12. 12
    Jason Frovich Says:

    thanks another great addon..
    Now if only there was a way to have this ping the servers when you add new content like wp..

  13. 13
    Physicist Says:

    Zorro:

    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.

    Apparently, the right solution is to replace
    $sitetitle = $mosConfig_sitename;
    to
    $sitetitle = htmlentities($mosConfig_sitename);
    in admin.ping.php

  14. 14
    Zorro Says:

    Thanks for the followup! I’ll make the adjustment you suggested.

    Kind regards,
    Zorro

  15. 15
    yurume Says:

    Thanks for

  16. 16
    Christian Says:

    Hi!
    I would like the component to send a ping for some specific files on our website (www.icity.se/blogg/username1, www.icity.se/blogg/username2, www.icity.se/blogg/username3 … etc).
    Is that possible to do?

  17. 17
    Physicist Says:

    Christian:
    I have not absolutely understood, what exactly you want. Please, describe it in more detail.

  18. 18
    Alberto Says:

    Work your plugin with Joomla 1.5.01?

  19. 19
    Physicist Says:

    Work your plugin with Joomla 1.5.01?

    I didn’t test it with Joomla!1.5.

  20. 20
    Donna Lien Says:

    Work great! Im  using it now. Thanks for this nice work for joomla user.
    Regards,
    Donna

  21. 21
    Productos de Asturias Says:

    This cannot even be installed on J!1.5, the installator refuses saying:

    Error! Could not find a Joomla! XML setup file in the package.

  22. 22
    Physicist Says:

    This component for Joomla!1.0.x only.
    I worked on new version of this component both for 1.0.x and 1.5.x, but I have no free time to finish it (I'll try to release it in July/August).

  23. 23
    Sachse Says:

    I become a error:
    Warning: fsockopen(): unable to connect to blogsearch.google.com:80 in /data/www//html/administrator/components/com_ping/admin.ping.php on line 40
    http://blogsearch.google.com/ping/RPC2
    Cannot open connection: Connection timed out (110)

    And this for all services…

    Whats wrong ?

  24. 24
    Physicist Says:

    Sachse, it means that your hoster doesn't allow connection to external sites.

  25. 25
    stefaan Says:

    any news about version joomla 1.5 ?

  26. 26
    tonyrocks Says:

    What is the status of a 1.5 version? :)

  27. 27
    kingbt Says:

    I`ll wait for a J1.5 version… thanks

  28. 28
    DREwno Says:

    any news about version Joomla 1.5? :(

  29. 29
    Brian Says:

    Hi there: Do you have any on the automatic ping for Joomla 1.5?

  30. 30
    Richard Says:

    Anxiously waiting on version for Joomla v1.5 !! Any status update?

  31. 31
    John Says:

    Interested in trying your Joomla! 1.5 ping add-on. Sound like a necessity for Joomla! Hope you get some free time to finish it up.

  32. 32
    Eric Says:

    When will this work natively for Joomla 1.5

  33. 33
    haji Says:

    Joomla 1.5 can not install

  34. 34
    Physicist Says:

    I make a version for J!1.5 and send it to several testers. If they don't find errors, I release it to public.

  35. 35
    Jordi Says:

    Any news about the new version for Joomla 1.5?

  36. 36
    haber Says:

    we are waiting for joomla 1.5 version of the component and also waiting for google autoping for joomla 1.5
    thanks for your work regards.

  37. 37
    adi Says:

    i hope this component support joomla 1.5. i will use it at http://baliseminyakvillasrental.com

  38. 38
    Chris Says:

    Any update on this for 1.5?

    Thanks

  39. 39
    Jewelosman Says:

    Hi,
    first of all i am sorry for my poor english. I am using Weblog ping component with joomla 1.0.15…i have added a server list which is given below…when i click Component -> Ping -> Ping ….browser work for sometime…after that one blank index2.php file autometically download..i cant see any success or failure messege.. is it working?

    http://api.moreover.com/RPC2
    http://api.my.yahoo.co.jp/RPC2
    http://api.my.yahoo.com/RPC2
    http://audiorpc.weblogs.com/RPC2
    http://blog.goo.ne.jp/XMLRPC
    http://blogpeople.net/ping
    http://blogsearch.google.com.br/ping/RPC2
    http://blogsearch.google.com.bd/ping/RPC2

  40. 40
    adikhresna Says:

    I try it as soon as download at joomla 1.5.8. but setup is error. Any new version for it?

  41. 41
    the last tickets Says:

    there is no news for joomla 1.5 component.

You can follow any responses to this entry through the RSS 2.0 feed.

Leave a Reply