For whatever reason, there appears to be some confusion as to what is going to take place with WordPress 2.6 and the XML-RPC feature. Although James brought the issue to light ( read
WordPress Disabling XML-RPC By Default With 2.6—Good or Bad? ) the confusion needs to be addressed in a seperate post. So here is the real deal.
- New installations of WordPress from 2.6 on will have XML-RPC disabled by default
- Those of you upgrading any previous version of WordPress to version 2.6 will not have XML-RPC disabled as part of the upgrade process.
- The feature is not disappearing nor is it being disabled indefinitely.
Thanks to Joseph Scott in the comments, I’ve learned that the team has changed the way in which this feature was implemented. Read more about it here.
Monday’s poll will ask the question, Which 3rd party blog publishing tool do you use? The results should give us a very rough estimate as to how popular using a third party blogging application is when compared to the built in publishing system.
4 thoughts on “Clearing Some Of The Confusion”
Thanks Jospeh, Will edit the post to reflect the change
That change was part of my patch set on disabling XML-RPC and AtomPub:
http://trac.wordpress.org/ticket/7157#comment:18
Ryan has committed them to -trunk.
Where did you end up getting that information as I can’t find that out anywhere using my sources.
The upgrade process has been changed so that XML-RPC & AtomPub will be left on for those upgrading to 2.6 to minimize confusion.
Comments are closed.