WordPress.org

Make WordPress Core

Changes between Initial Version and Version 4 of Ticket #14902


Ignore:
Timestamp:
02/03/2015 05:06:21 AM (7 years ago)
Author:
dd32
Comment:

The original page mentioned in the ticket no longer exists, however http://www.weblogs.com/api.html and https://developer.twingly.com/resources/rpc-ping/ agree's with the original ticket, while http://blo.gs/ping-example.php & others disagree's (and agrees with core).

It'd be really nice if I could find a extendedPing spec that isn't hosted itself by a weblogupdates provider.. or at least one that the others referred to.

It seems that WordPress has simply always done this wrong, not sure for what reason, for reference r2572 was when the current code was added. It also seems commonly accepted that most servers simply ignore the extra parameters, or handle a RSS feed perfectly okay, which also makes sense as the RSS feed should have updated at the same time as the post/page itself.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14902

    • Property Owner set to josephscott
    • Property Status changed from new to reviewing
    • Property Keywords needs-patch added; xmlrpc ping pingomatic removed
  • Ticket #14902 – Description

    initial v4  
    55That function first attempts an XMLRPC call to the service's weblogUpdates.extendedPing.  If that fails, it attempts to notify weblogUpdates.ping.
    66
     7{{{
    78if ( !$client->query('weblogUpdates.extendedPing', get_option('blogname'), $home, get_bloginfo('rss2_url') ) ) // then try a normal ping
    89        $client->query('weblogUpdates.ping', get_option('blogname'), $home);
     10}}}
    911
    1012'''1) The weblogUpdates.extendedPing does not match the published standard.'''