Title: XML-RPC Fixes
Last modified: August 18, 2016

---

# XML-RPC Fixes

 *  [Dougal Campbell](https://wordpress.org/support/users/dougal/)
 * (@dougal)
 * [22 years, 5 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/)
 * I think I have most of the bugs stomped out of the XML-RPC API interfaces now.
   Most of the big ones were squished over the last few days with the help of the
   ecto developer. And I just committed fixes for the last of the outstanding problems
   with timestamps that I was aware of.
    If you are tracking CVS, watch for xmlrpc.
   php revision 1.39. Or test against any nightly dated 2004-03-17 or later. If 
   you had problems with your favorite blog client before, please try again, and
   post your results here.

Viewing 15 replies - 1 through 15 (of 15 total)

 *  [garth](https://wordpress.org/support/users/garth/)
 * (@garth)
 * [22 years, 5 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-40686)
 * post_name is still not being set. see my post at
    [http://wordpress.org/support/4/3276](http://wordpress.org/support/4/3276)
   thanks!
 *  Thread Starter [Dougal Campbell](https://wordpress.org/support/users/dougal/)
 * (@dougal)
 * [22 years, 5 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-40716)
 * Patched and committed. Thanks for bringing it to my attention.
 *  [luhmann](https://wordpress.org/support/users/luhmann/)
 * (@luhmann)
 * [22 years, 5 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-40754)
 * I don’t know if it has been fixed or not, but the last nightly build still didn’t
   provide a post slug for entries submitted with ecto.
 *  Anonymous
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41022)
 * I downloaded xmlrpc.php version 1.40 on March 21 and installed it in my WordPress
   1.0.1 site. I tried blogging from NewzCrawler version 1.6.4 build 1989, the latest
   release, and the only XML-RPC API available that works is Blogger. The only XML-
   RPC API choices in NewsCrawler under the Blog Service=Custom setting are Blogger(
   the original), MetaWeblog, Blogger 2.0, Movable Type, and LiveJournal. Movable
   Type, as you know, supports multiple categories. I can’t remember whether MetaWeblog
   does, and I don’t know about Blogger 2.0 or LiveJournal. Perhaps the WordPress
   developers and other WordPressers need to have a chat with the NewzCrawler developer
   so WordPress and its XML-RPC API is one of the supported Blog Services. I’ve 
   just made the suggestion myself to [info@newzcrawler.com](https://wordpress.org/support/topic/xml-rpc-fixes/info@newzcrawler.com?output_format=md)—
   David Mattison, [http://www.davidmattison.ca/wordpress](http://www.davidmattison.ca/wordpress)
 *  [luhmann](https://wordpress.org/support/users/luhmann/)
 * (@luhmann)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41026)
 * Things seem to be working fine with ecto as of this morning’s (3/21) CVS.
 *  Moderator [Matt Mullenweg](https://wordpress.org/support/users/matt/)
 * (@matt)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41029)
 * David, you can’t mix and match from 1.0.x and the CVS, because there were database
   changes between then so xml-rpc.php actually functions differently in addition
   to the bugfixes.
 *  [erogers](https://wordpress.org/support/users/erogers/)
 * (@erogers)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41039)
 * Any timeline for including the RPC changes in a release version?
 *  Thread Starter [Dougal Campbell](https://wordpress.org/support/users/dougal/)
 * (@dougal)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41063)
 * We probably will not back-port these fixes for the 1.0.x releases. They will 
   be in the next official release version.
    There is no “WordPress API”. We are
   compatible with the other standard APIs: Blogger, metaWeblog, and MovableType.
   These are listed in order from simplest to most-capable. In my testing, it is
   now possible to post to WordPress (1.2alpha) using NewzCrawler’s MovableType 
   API support. Though, NC uses some ugly HTML, when formatting posts 😉
 *  [erogers](https://wordpress.org/support/users/erogers/)
 * (@erogers)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41071)
 * Makes sense to wait for the next release, I was asking when that would be. My
   only complaint about WP was finding out that it really isn’t compatible with 
   the standard APIs as it claimed to be. I realize that 3rd-party client compatibiltiy
   is just one part of standards compliance, but for many people it is one of the
   most important parts.
 *  Anonymous
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41134)
 * Thanks for pointing out that I can’t mix and match the CVS code with the latest
   release. Bummer. I just tried w.bloggar using the same setup as I have with NewzCrawler.
   I’ll go back to the original 1.0.1 xmlrpc.php file. — David Mattison, [http://www.davidmattison.ca/wordpress](http://www.davidmattison.ca/wordpress)
 *  Thread Starter [Dougal Campbell](https://wordpress.org/support/users/dougal/)
 * (@dougal)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41140)
 * In my previous testing, [w.bloggar](http://wbloggar.com/) (Blogger/b2/metaWeblog
   API) and [Zempt](http://zempt.com/) (MovableType API) both worked fine with the
   1.0.x releases. Since those were pretty much the only clients I tested with, 
   I wasn’t aware of the API problems until I started hearing reports from people
   using other clients. So, with 1.0.x, those two clients are your best bet.
    With
   the fixes in WP 1.2, pretty much every client should work. And if anybody finds
   one that doesn’t, I’ll do my best to fix it.
 *  Anonymous
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41209)
 * Hello , I have installed the latest Build of WP and now Ecto and NetNewsWire 
   both post just fine, but the posts do not publish, even though they say they 
   are published. I delete them and repost them thru the web interface and the same
   story posts just fine. ….. Hmmmm.
    Brian [http://urhentime.com/](http://urhentime.com/)
 *  [luhmann](https://wordpress.org/support/users/luhmann/)
 * (@luhmann)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41210)
 * I find there is a delay with publishing via ecto. Sometimes you have to wait 
   a minute before the post appears.
 *  Anonymous
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41211)
 * Thanks! Ill give it another try.
 *  [rayne](https://wordpress.org/support/users/rayne/)
 * (@rayne)
 * [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41212)
 * I installed 1.02 this past week and I am unable to post via Zempt or wbloggar.
   I am getting an error. It tells me only one top level element is available in
   a document. I’d like to be able to post with either of these clients. Please 
   help me figure out why I am not able to.

Viewing 15 replies - 1 through 15 (of 15 total)

The topic ‘XML-RPC Fixes’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 15 replies
 * 7 participants
 * Last reply from: [rayne](https://wordpress.org/support/users/rayne/)
 * Last activity: [22 years, 4 months ago](https://wordpress.org/support/topic/xml-rpc-fixes/#post-41212)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
