This is the article that I had originally intended to post last week, before I suffered a self-induced glitch which caused me to lose my work-in-progress. Thanks to my friend Geof Morris who prompted me to double-check my database for saved revisions. As it turns out, there was indeed a revision stored there which did not show up in the list of revisions given in the editor. [...]
This is the first installment of “WordPress Wednesday”, which I mentioned in my previous post about making changes to my site. This first one is going to be a little long, and I’ve been editing the draft off-and-on for over a week. [...]
I’m surprised that I haven’t seen mention of this from other channels yet (official or unofficial), but two days ago, SVN revision 8561 of the WordPress 2.6 branch was labled as WordPress version 2.6.1-beta1. The log messages reveal that most changes since the 2.6 release are minor bug and typo fixes. . [...]
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:
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:
When I’m putting a new web site together, one thing that sometimes bugs me is choosing which fonts to use. I’ll typically throw together a list of fonts that I like, decide to use this set of serif fonts for these page elements, and that set of sans-serif fonts for those other elements, select some fallback choices for my stylesheet, and let it go at that. Obviously, I’m no designer — or I’d be saying ‘typeface’ instead of ‘font’ — but I’d like to be able to make ‘better’ choices for my fonts.
I’ve done a little bit of searching, but I haven’t found what I’m looking for. [...]
If you run a busy WordPress site, or even if your site just has a lot of processor-intensive plugins, then you probably already run the WP-Cache plugin (plugin directory, original announcment, recent security update info). Even though my site isn’t super busy, my server is a little light in the RAM department, and using WP-Cache helps the box keep up with requests better.
One minor annoyance, however, is that with WP-Cache enabled, my syndication feeds aren’t delivered with the correct Content-Type. [...]
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. [...]
A while back, the WordPress development team decided to aim for date-targeted, quarterly releases, to speed up the development cycle. One of the main things this does is to give more frequent updates, but with fewer “big” new features in each release. The target for WordPress 2.2 was set for around April 23.
One of the new features in WordPress 2.2 is ‘tags’. For any of you who still don’t know what tags are, they are basically keywords that you can put on posts. [...]
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. [...]
