Last night Ryan Boren announced the release of WordPress 2.6 Beta 1. At first glance, you probably wouldn’t notice much difference between versions 2.5 and 2.6. The two biggest new features are Post Revisions, which saves a history of edits made to each post, and support for Gears, which greatly speeds up working with the admin screens.
Other changes of note:
WordPress 2.2 “Getz” is now official. I’ve listed some of the changes previously, but here’s another quick rundown:
You can find a list of changes for version 2.2 on the WordPress Trac site. [...]
That’s right, two shiny new bugfix/security updates. One for the 2.0 branch and one for the 2.1 branch. There are some small bugfixes in both of these versions, but the main reason to upgrade is for the security fixes (I’m going to write more on that subject later).
Visit the downloads page for version 2.1.3, and the Release Archive for version 2.0.10.
Watch later this month for the release of WordPress 2.2. [...]
For those of you who never install “dot-zero” software releases, now is probably a good time to upgrade to WordPress 2.0.1.
All in all we’ve closed 114 bugs in the 2.0.1 release, which you’re welcome to check out if you’re curious about every fix. . [...]
In case you didn’t already see my post over on the WordPress Development Blog, rest assured that WordPress is safe from the recently announced PHPXMLRPC worm. Some of the articles about this worm point to old information indicating that WP 1.5 is vulnerable, but that is incorrect. Versions 1.2.x and earlier are in danger, however. . [...]
Announcing WordPress 1.5.2, now available for download. Owen Winkler has a good plain-English description of the changes.
There is a security-related bugfix in this release, which affects servers that have register_globals turned on (which you shouldn’t). . [...]
I’ve never been too big on SOAP. It’s nice that there are lots of toolkit implementations out there, but for most of my projects, it just seems like overkill. Many developers joke about the acronym being an oxymoron, because SOAP can quickly lose its simplicity. XML-RPC has its faults, but it’s easier to test and debug, in my experience. [...]
It’s been over two weeks since my last update. I’m sure that it’s been terribly distressing to the three people who actually read this site. My only excuse is that I’ve been insanely busy, because a lot of things have been going on. Here’s a quick brain dump, which may or may not be in chronological order:
We finally found time to do some more work on Ping-O-Matic, and have implemented an XML-RPC interface. You can now send a standard weblogs.com compatible ping to http://rpc.pingomatic.com/ and we will ping a subset of our services. Currently, this is a fixed subset of seven services:
In the future, we will have ways for you to customize which services you would like us to ping on your behalf. [...]
Update on WordPress blog APIs
I mentioned previously that the XML-RPC and Atom blog APIs would be disabled by default when WordPress 2.6 is released. This was a matter of some debate within the community, and there has been some clarification: