See elliptical for details. Please comment here or there with problems, concerns, or comments.

He’s getting the same message that I am, but doesn’t have xmlrpc logging turned on, so we can’t verify that he’s having the same precise problem that I am, so I still don’t know for sure that the problem I think I see in my log is caused by the interaction between OPML Editor and WP or whether it’s something on my server. Anyone who’s got xmlrpc logging tuned on (or can turn it on) willing to give it a whirl?
Next step is for me to make OPML Editor skip over some of the whitespace handling that it does to see if something in there is causing the munging.

See my conversation with Dave starting here.

When I step through the code I get what appears to be a valid xmlrpc method call over http, but my xmlrpc log file looks munged.  If there’s anyone around who uses a WordPress 1.5+ blog and the OPML Editor and woud be willing to try a post, I’m interested to see if you have the same problems or if the issue is on my server.

I tried Dave’s wordPress.root tool or the OPML Editor to create a new post at elliptical this evening, and it seems as though the inplementation of the MetaWeblog API in OPML Editor is different than that in Flock, because Flock’s blogging tool works just fine while the OPML Editor’s tool won’t authenticate me to xmlrpc.php.

Here’s what the log file records from Flock (actual post data removed for clarity):

2005-11-10 19:38:50 Input: <?xml version=”1.0″?>
<methodCall><methodName>metaWeblog.newPost</methodName><params>
<param><value><string><![CDATA[1]]></string></value></param>
<param><value><string><![CDATA[username]]></string></value></param>
<param><value><string><![CDATA[password]]></string></value></param>
<param><value><struct><member><name>title</name><value><string><![CDATA[post title]]></string></value></member>
<member><name>description</name><value><string><![CDATA[post text]]></string></value></member>
<member><name>mt_tb_ping_urls</name><value><array><data><value><string><![CDATA[ping urls]]></string></value></data></array></value></member></struct></value></param>
<param><value><boolean>0</boolean></value></param></params></methodCall>
and here’s what’s recorded from OPML Editor:

2005-11-24 00:28:55 Input: <?xml version=”1.0″?>^M
<methodCall>^M
<methodName>metaWeblog.newPost</methodName>^M
<params>^M
<param>^M
<value><i4>0</i4></value>^M
</param>^M
<param>^M
<value>username</value>^M
</param>^M
<param>^M
<value>password</value>^M
</param>^M
<param>^M
<value><struct>^M <member>^M <name>description</name>^M <value>^Mwhat’s the log say?</value>^M </member>^M <member>^M <name>title</name>^M <value>test for kinrowan.net</value>^M </member>^M </struct></value>^M
</param>^M
<param>^M
<value><boolean>1</boolean></value>^M
</param>^M
</params>^M
</methodCall>

Among the oddities are the presence of the “^M” strings at the end of each line.

Also strange is that OPML Editor is able to communicate just fine with WordPress.com blogs, and so is Flock.

Here’s the error message I get:

Hmmmm.

Nevertheless the wordPress.root tool is really cool – being able to use the OPML Editor to post here is boon enough!