WordPress 3.4 finally shipped a few weeks ago, and now attention turns to 3.5. Feature discussions will start at the July 11 IRC dev chat, but in the meantime there will be a sprint to revise the unit tests suite. This post is to serve as starting guidance for the contributors who will be helping in this sprint. For background, you can read the kickoff IRC chat logs.
Today I gave a talk on “Integrating with WordPress via XML-RPC” at WordCamp NYC:
If you have any questions or follow-ups, please reach me via the comments or contact form.
As WordPress 3.4 approaches RC and final release, the new features in the XML-RPC API have finally stabilized. For those Python users out there, I’ve updated my Python binding library to take advantage of the new functionality.
If you are currently using a previous release (1.x) of the library, be warned that 2.0 is not backwards compatible. I’ve removed all but one use of legacy Blogger/metaWeblog methods, which has caused the posts module and several others to change significantly. See the changelog for full details.
I’ve released another update of my XML-RPC modernization plug-in for WordPress. This release incorporates the work from Ticket #18429, and adds new wp.newPost, wp.editPost and wp.deletePost methods. With these new methods, full CRUD capabilities for posts of any type (posts, pages, and any registered custom post types) are available through XML-RPC.
After half a year of complaining about the state of XML-RPC in WordPress, I’ve tried to get the stars aligned for some significant improvements in the next release (3.4). The 3.4 development cycle has just begun after the release of 3.3 last week, and I am currently on winter break until spring semester classes start on January 9. Some of the core developers have shown interest in seeing XML-RPC improved, so I hope to make their job easier by doing the legwork on patches.
As of today (12/22/2011), there are 72 open tickets in the WordPress core Trac XML-RPC component. While I’d love to see them all fixed, there is limited amount of time and so we must prioritize. This post represents my current priorities and plans. Read More…
Prior to the 3.0 release of WordPress, I often dismissed WordPress as “just a tool for blogging.” Much to the credit of the core developers and community, WordPress has become much better suited for projects that are more complex than reverse-chronological blogging.
But when I try to use WordPress as a CMS, one of my biggest remaining stumbling blocks is the difficulty of integrating with other systems.
As I discussed last time, the WordPress app for Windows Phone was recently updated for compatibility with the 7.5 (“Mango”) OS update. With that out of the way, I’d like to see the app undergo some UI/UX improvements to make it feel less like a ported Android app and more like a native Metro-style WP7 app.