I am doing some fact checking on an article about optimal WordPress ping setup and usage in v.3.5. Could one of the WP developers verify a few things for me, please?
First, how does WP 3.5 handle pinging of repeated post edits? I found conflicting information on wordpress.org.
However, Chip Bennett, over on his cbnet Ping Optimizer plugin page recently stated (2012-12-20) that, based on information from @otto42, “When you edit an existing post, it won’t send any unnecessary ping to ping services and saves your blog from getting banned by such services.” Because, “WordPress intelligently fires pings when a post is edited, by keeping track of previous successful pings and not re-pinging them.”
If Chip’s statements are correct, could you elaborate in a bit more detail how WP ‘intelligently fires pings’? And, in what instances WP will re-ping an edited post?
Also, why doesn’t WP 3.5 use Weblogs.com’s published standard for extended pings and include the exact post URL of new and updated posts when pinging update services? There is a two year old, unresolved ticket, #14902 (weblogUpdates.extendedPing does not implement standard), about this issue.
Finally, do you know if Ping-o-matic’s API supports Weblog’s standard? The manual submission on the homepage clearly does not, but what about their API? Several ping plugins support the standard, but if Ping-o-matic doesn’t, then it is ultimately a worthless feature for many people.
Thanks for your help.
- The topic ‘Pinging Update Services’ is closed to new replies.