Perhaps MT.pm instead
Trying the blo.gs ping stuffed into MT.pm, where MT does its calls to MT::XMLRPC, instead. Perhaps it will be better behaved there. I would have liked to redo the whole ping subroutine, since it currently dies on the first error (say, pinging weblogs.com returns an error: you don’t get to ping anything else, including the MT recently updated), but I’m not bright enough. Luckily, that’s supposed to be on the “to fix” list, and I see by the comments in MT.pm that pinging clouds other than weblogs.com is also on the list. The only thing I like better than hacking in a temporary solution is to see an official permanent solution instead.
<update>Works for me, but then it worked for me before. We’ll see whether it does the trick for Shannon.</update>
<update number=”2″>Takes care of the problems in Shannon’s blog, too.</update>
So, if hacking CMS.pm doesn’t work for you, try this:
- Edit /mt/lib/MT.pm
- Find the line in
sub ping
that readsMT::XMLRPC->weblogs_ping($blog) or return $mt->error(MT::XMLRPC->errstr);
(displayed on two lines, but it’s one line of code) - Insert a new line immediately after that, that reads:
MT::XMLRPC->ping_update('weblogUpdates.ping', $blog, 'http://ping.blo.gs/') or return $mt->error(MT::XMLRPC->errstr);
Save, reupload, publish a new post, and check blo.gs and weblogs.com.
Installation #2? What am I, a fucking NUMBER?
Yeah, and you’re damn lucky just to be number two. None of yer lip, girl.
All right then. Give me back my underwear.
Okay, I’ll un-number you, then.
My email address doesn’t show up in your comments anymore. I will adapt.
Is this still how it needs to be done in MT 2.2?
I’ve got to clean up this spread around bunch of posts. No, the 2.2 update is in the comments of the other post.
Updated for MT 2.5 : no need to hack, just go to Blog Config -> Preferences -> Publicity, and check the box to ping blo.gs.