UPDATE: Steve Jensen brings up a good point in his post – that all instances of user_login ($args[1]) and user_password ($ars[2]) need to be trimmed in order for other method calls (like “edit”) to succeed. xmlrpc.php.txt has been updated.

As long as you’re able to replace files on your WordPress install, my hack will fix the authentication problems many of us have been seeing with using OPML Editor to post to stand-alne WordPress blogs. Here’s the how-to:

• download xmlrpc.php.txt.
• on your server, make a back up of the existing xmlrpc.php file, or rename it xmlrpc_bak.php. It’s typically in the wordpress folder in your installation (look at the options screen in your admin control panel and find “WordPress address (URI)” if you don’t know where that is).
• upload the new xmlrpc.php.txt file to that location and rename it to xmlrpc.php
• set up OPML Editor’s wordPress.root Prefs to use your stand-alone blog:

  

• rock on.

This change will be overwritten by later WordPress upgrades and has only been tested (by me) on WordPress 1.5.2. I believe it will work just fine for anything above 1.5 but have no idea about earlier versions. I’m going to look into submitting the change for the next version of WordPress but have no idea how likely that is to happen.

Use at your own risk and your mileage may vary and all the usual disclaimers apply. Please leave comments or concerns here.

For those who care, the issue was that Dave’s xmlrpc post added whitespace to the parameters, making the username and password have a sizeable amount of whitespace before the actual values. Trimming the variables did the trick.

This entry was posted on Thursday, November 24th, 2005 at 7:46 pm and is filed under Blogging, OPML, WordPress .
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.