Page 1 of 1

event plugin order for xmlrpc -> announce?

Posted: Wed Dec 28, 2005 1:22 am
by ripp
s9y is working beautifully for me :) except for one minor niggle I've found.

I've been posting via the XML-RPC plugin, and when I do this, it does not run the new posts through the 'Announce' plugin, sending pings off to the various tracbacks/pings....

What order should the XMLRPC and announce plugin be in for this to work? Or is this just a bug and I'll have to live w/ it (unfamiliar w/ the API yet or I'd have a go at it)

TIA.

Re: event plugin order for xmlrpc -> announce?

Posted: Wed Dec 28, 2005 7:24 pm
by garvinhicking
Baiscally the order of plugins in this case should not matter.

Which XML-RPC Api do you use, MT or Blogger? Which client do you use? Which version off the MXL-RPC and Serendipity?

Regards,
Garvin

Posted: Wed Dec 28, 2005 8:01 pm
by ripp
using S9Y 0.9.1, XMLRPC plugin is: 1.9, Announce is: 1.02, on php-cgi 4.4.1

I've been using the 'Performancing' Firefox extension (http://performancing.com/firefox .. kinda slick) using the MovableType API...

It can use the following API's: Wordpress (didn't work), MT, Drupal, TextPattern, Blogger API, and MetaWebLog API, and optionally an 'API Key' which I'm currently not using (but probably should)

Haven't tried using any other API, could it make a difference?

Posted: Wed Dec 28, 2005 9:24 pm
by garvinhicking
Can it be that entries written with "performancing" are saved as "Draft" status?

Because only "Publish" type entries would be announced to the plugin. As far as I can trace the code, the only way that the Announce Entries plugin does not get executed is, when the entry's status is "draft".

In case you might want to get your hands dirty, you could enable the XML-RPC plugin'S debugging facility. Just edit the serendipity_xmlrpc.inc.php file within the plugin directory and look at the $debug_xmlrpc variable; if you set that to true, a logfile at /tmp will be created which you can inspect.

You might need to disable all ob_start() and ob_clean() calls within that file (temporarily) so that all output from the plugin is piped through to the logfile.

You might want to try the "Flock" browser, which seems to have better API support yet. "w.bloggar" is also an application that should work well...

HTH,
Garvin