Dougal Campbell's geek ramblings

If you already run WordPress, then you’ve probably seen the other announcements in your Dashboard about the release of WordPress 2.5. There are plenty of details in the Development Blog posting, so I won’t rehash the feature list here. I’ll just point out a few important details.

First of all, in my post about Release Candidate 1, I mentioned that I had problems with the plugin updater. Since that time, I have been able to upgrade complex plugins with out a problem. I didn’t do extensive testing, but I feel like this is probably safer now. Other folks on the wp-testers mailing list have reported observed improvements similar to mine.

Next, I’ll point out that since the introduction of the WYSIWYG editor back in version 2.0, I have always stuck to the “Code” editor. And on top of that, I have disabled the auto-formatting (wptexturize and wpautop) filters. I’ve always entered every bit of HTML within my posts by hand. Starting with version 2.5, I’m going to relax my grip and hand the reigns back over to the system. I’ve disabled my “untexturize” plugin, and switched to the “Visual” editor as my default. The Visual editor should be just fine for most of the posts that I write. And on those occassions when I need to do something advanced (like <code>, <ins> or <del> tags, my standard “pull-quote” div for images, etc), I can seamlessly switch to the HTML view and back, without worrying about the Visual editor messing with my manual edits later.

And for those of you who might wonder, but haven’t seen it mentioned, the new improvements will be filtering into WordPress.com and the WordPress-MU codebase very soon.