• Translation of role names fixed
• wp_page_menu() defaults to sorting by the user specified menu order rather than the page title
• Upload error messages are now correctly reported
• Autosave error experienced by some IE users is fixed
• Styling glitch in the plugin editor fixed
• SSH2 filesystem requirements updated
• Switched back to curl as the default transport
• Updated the translation library to avoid a problem with mbstring.func_overload

Thanks again for testing WordPress.

• Certain themes were calling get_categories() in such a way that it would fail in 2.8. 2.8.1 works around this so these themes won’t have to change.
• Dashboard memory usage is reduced.  Some people were running out of memory when loading the dashboard, resulting in an incomplete page.
• The automatic upgrade no longer accidentally deletes files when cleaning up from a failed upgrade.
• A problem where the rich text editor wasn’t being loaded due to compression issues has been worked around.
• Extra security has been put in place to better protect you from plugins that do not do explicit permission checks.

If you would like to automatically upgrade from 2.8 to 2.8.1 Beta 1, follow these instructions.  Thanks for testing WordPress.

The first thing you’ll notice is that visually 2.8 feels a lot like 2.7, just with some minor tweaks here and there. However once you’ll dig in you’ll begin to appreciate the changes.

Major New Improvements

First and foremost, 2.8 is way faster to use. We’ve changed the way WordPress does style and scripting.

The core and plugin updaters in previous versions of WordPress have been such a success we decided to bring the same to themes. You can now browse the entire theme directory and install a theme with one click from the comfort of your WordPress dashboard.

If you make edits or tweaks to themes or plugins from your dashboard, you’ll appreciate the new CodePress editor which gives syntax highlighting to the previously-plain editor. Also there is now contextual documentation for the functions in the file you’re editing linked right below the editor.

If you were ever frustrated with widgets before, this release should be your savior. We’ve completely redesigned the widgets interface (which we didn’t have time to in 2.7) to allow you to do things like edit widgets on the fly, have multiple copies of the same widget, drag and drop widgets between sidebars, and save inactive widgets so you don’t lose all their settings. Developers now have access to a much cleaner and robust API for creating widgets as well.

Finally you should explore the new Screen Options on every page. It’s the tab in the top right. Now, for example, if you have a wide monitor you could set up your dashboard to have four columns of widgets instead of the two it has by default. On other pages you can change how many items show per page.

And Even More

You can read the full list of over 180 new features, changes, upgrades, and improvements on the Codex. The list is exhausting!

The Future

We’re already thinking hard about the next versions, 2.9 and 3.0. Keep an eye out for improved media handling, better dependency checking, versioning of templates and themes, and of course the fabled merging of WordPress and MU announced at WordCamp San Francisco two weeks ago.

What’s new? All of this.

Good hunting, all you testers.

You may have noticed that we went much longer than usual to release this .1 update. We’re very proud of this fact because it’s a testament to the testing all of you contributed prior to the release of 2.7 which helped make it the most bug-free release we’ve had.

Consult the list of fixed tickets and the  full set of changes between 2.7 and 2.7.1 for details.

Finally partly due to the stability of the 2.7 we’ve decided to push back 2.8 a few more weeks so we can bring in a few more speed optimizations, taxonomy enhancements, and new theme features. We also need to figure out which jazz musician to name the release after.

Next you’ll begin to notice the new features subtly sprinkled through the new interface: the new dashboard that you can arrange with drag and drop to put the things most important to you on top, QuickPress, comment threading, paging, and the ability to reply to comments from your dashboard, the ability to install any plugin directly from WordPress.org with a single click, and sticky posts.

Digging in further you might notice that every screen is customizable. Let’s say you never care about author on your post listings — just click “Screen Options” and uncheck it and it’s instantly gone from the page. The same for any module on the dashboard or write screen. If your screen is narrow and the menu is taking up too much horizontal room, click the arrow to minimize it to be icon-only, and then go to the write page and drag and drop everything from the right column into the main one, so your posting area is full-screen. (For example I like hiding everything except categories, tags, and publish. I put categories and tags on the right, and publish under the post box.)

For a visual introduction to what 2.7 is, check out this video (available in HD, and full screen):

It’s all about you. It’s the next generation of WordPress, which is why we’ve bestowed it with the honor of being named for John Coltrane. And you can download it today.

Last, but certainly not least, this may be the last time you ever have to manually upgrade WordPress again. We heard how tired you were of doing upgrades for yourself and your friends, so now WordPress includes a built-in upgrade that will automatically notify you of new releases, and when you’re ready it will download them, install them, and upgrade your blog with a single click.

(As with any interface change it may take a little bit of time to acclimate yourself but soon you’ll find yourself whizzing through the screens. Even people who have hated it at first tell us after a few days they wonder how they got by before.)

The Story Behind 2.7

The real reason Coltrane is such a huge leap forward is because the community was so involved with every step of the process. Over 150 people contributed code directly to the release, our highest ever, with many tens of thousands more participating in the polls, surveys, tests, mailing lists, and other feedback mechanisms the WordPress dev team used in putting this release together.

For some of the back story in the development of 2.7, check out these blog posts (thanks to WeblogToolsCollection for the list):

• Usability Testing Report: 2.5 and CrazyHorse
• The New 2.7 Dashboard
• The Visual Design of 2.7
• WordPress 2.7 wireframes
• Comprehensive Codex Article on WordPress 2.7
• WordPress Development Updates from Jane Wells
• WordPress Usability Testing in New York
• WordPress 2.7 UI Configurability from Ryan Boren
• Customizable Post Editing Screen from Mark Jaquith
• WordPress 2.7 Navigation Survey from Jane Wells
• Shortcuts/Favorites Menu from Jane Wells
• CrazyHorse Presentation at WordCamp SF
• WordPress 2.7 Walkthrough by Matt
• WordPress 2.7 and beyond from Matt at WordCamp Utah

This was interesting to us, a blogging software release we actually blogged about, but the process was hugely informative. Prior to its release today Crazyhorse and 2.7 had been tested by tens of thousands of people on their blogs, hundreds of thousands of you count .com. The volume of feedback was so high that we decided to push back the release date a month to take time to incorporate it all and do more revisions based on what you guys said.

For those of you wondering why we didn’t call this release 3.0, it’s because we abhor version number inflation. 3.0 will just be the next release after 2.9. The major features in new point releases approach also works well for products like OS X, with huge changes between a 10.3 and 10.4.

The Future

Those of you following along at home might have noticed this was our second major redesign of WordPress this year. Whoa nelly! While that wasn’t ideal, and I especially sympathize with those of you creating books or tutorials around WordPress, there’s good news. The changes to WordPress in 2.5 and 2.7 were necessary for us to break free of much of the legacy cruft and interface bloat that had built up over the years (gradually) and more importantly provide us with a UI framework and interface language we can use at the foundation to build tomorrow’s WordPress on, to express ideas we haven’t been able to before. So at the end of 2009 I expect, interface-wise, WordPress to look largely the same as it does now.

That said, we couldn’t be more excited about the future with regards to features. Now that we’ve cleared out more basic things, we are looking forward in the coming year to really tackling media handling including audio and video, better tools for plugin and theme developers, widgets, theme updates, more integrated and contextual help, and easier integration with projects like BuddyPress and bbPress.

Thank Yous

We would like to take a moment to thank the following WordPress.org users for being a part of 2.7: Verena Segert, Ben Dunkle, 082net, _ck_, Aaron Brazell, Aaron Campbell, Aaron Harp, aaron_guitar, abackstrom, Alex Rabe, Alex Shiels, anderswc, andr, Andrew Ozz, andy, Andy Peatling, Austin Matzko, axelseaa, bendalton, Benedict Eastaugh, Betsy Kimak, Björn Wijers, bobrik, brianwhite, bubel, Byrne Reese, caesarsgrunt, capripot, Casey Bisson, Charles E. Frees-Melvin, Chris Johnston, codestyling, corischlegel, count_0, Daniel Jalkut, Daniel Torreblanca, David McFarlane, dbuser123, Demetris Kikizas, Dion Hulse, docwhat, Donncha O Caoimh, Doug Stewart, Dougal Campbell, dsader, dtsn, dwc, g30rg3x, guillep2k, Hailin Wu, Hans Engel, Jacob Santos, Jamie Rumbelow, Jan Brasna, Jane Wells, Jean-LucfromBrussels, Jennifer Hodgdon, Jeremy Clarke, Jérémie Bresson, jick, Joe Taiabjee, John Blackbourn, John Conners, John Lamansky, johnhennmacc, Joost de Valk, Joseph Scott, kashani, Kim Parsell, Lloyd Budd, Lutz Schröer, Malaiac, Mark Jaquith, Mark Steel, Matt Freedman, Matt Mullenweg, Matt Thomas, matthewh84, mattyrob, mcs_trekkie, Michael Adams, Michael Hampton, MichaelH, mictasm, Mike Schinkel, msi08, msw0418, mtekk, Nick Momrik, Nikolay Bachiyski, Noel Jackson, Otto, Ozh, paddya, paul, pedrop, pishmishy, Po0ky, RanYanivHartstein, raychampagne, rdworth, reinkim, rickoman, rm53, rnt, Robert Accettura, roganty, Ryan Boren, Ryan McCue, Sam Bauers, Sam_a, schiller, Scott Houst, sekundek, Shane, Simek, Simon Wheatley, sivel, st_falcon, stefano, strider72, tai, takayukister, techcookies, Terragg, thinlight, tott, Trevor Fitzgerald, tschai, Txanny, Valiallah (Mani) Monajjemi, Viper007Bond, Vladimir Kolesnikov, wasp, wet, wfrantz, x11tech, xknown, xorax, ydekproductions, yoavf, yonosoytu, yoshi, zedlander

We think RC1 is ready for everyone to try out.  Please download RC1 and help us make the final release the best it can be.  As always, back up your blog before upgrading.

Get RC1.

• Numerous style improvements and refinements.
• All admin notices now go under the page title.
• PHP Notice fixes.
• Dashboard widget options now properly save.
• Menu fixes.
• New design for Quick Edit.
• Canonical feed URL fixes.
• Walker fixes.
• An update for Hello Dolly.
• Plugin installer updates.
• Numerous font updates.
• Updated login logo.
• Switch position of “Save Draft” and “Preview” buttons in publish module.
• File upload support for MS Office 2007+ file formats.
• Media upload buttons won’t show if the user doesn’t have the upload capability.
• Canonical redirects only do yes-www or no-www redirection for domains.
• Shift-click checkbox range selection improvement.
• Add New User page now separate.
• Tag suggest only suggests tags (not other taxonomy terms).
• QuickPress shows “Submit for Review” if user cannot publish.
• Private posts/pages, and password-protected posts/pages are rolled into new “Visibility” section of publish module.

If you have already installed Beta 1 or Beta 2, you can update to Beta 3 via the Tools -> Update menu. If you have problems, or if this is your first time in the 2.7 beta ring, you can download and upgrade the old fashioned way.

Get 2.7 Beta 3.

• The Upload button didn’t always show. Fixed.
• JS on the Dashboard broke for blogs with no comments, causing several UI elements to “freeze”. Fixed.
• Recent Drafts Dashboard module didn’t show correct times. Fixed.
• Various Autosave fixes.
• Redirect after deleting a page from the editor went back to the deleted page. Fixed.
• Fixed loading of translations for default TinyMCE plugins.
• Added avatars to the edit users list.
• Added some missing translations.
• Fixed some validation errors.
• Fixed some PHP warnings and notices.
• Handle inconsistent file permissions during auto upgrade
• Change Publish box layout to better accommodate internationalized text
• Fix quick editing of the last page in the Edit Pages list
• Fix Screen Options for IE
• Fixes for choose tag from tag cloud
• Rewrite rules fixes for certain hosts
• Don’t check for updates on every page load
• Easier post box dropping
• Preview fixes
• RTL fixes
• Fixed broken wp-mail
• Plugin update and install fixes
• First draft of contextual help tab

If you have already installed beta 1, you can update to beta 2 via the Tools -> Update menu.  Beta 1 does have a bug in the automatic upgrade that breaks certain setups, so be prepared to download and install Beta 2 manually if you experience problems.

Get 2.7 Beta 2.

Speaking of the final release, it will not be available on November 10th as originally scheduled.  We are two weeks behind schedule at the moment.  We need a little more time to finish the visual design, do a round of user testing against that finished design, and do a proper round of public beta testing. Our plan is to keep working as if Nov. 10 is still the release date.  However, instead of releasing the final 2.7 on the 10th, we will make a release candidate available instead.  The release candidate is intended to be a high-quality, almost-finished release that we are comfortable recommending for broad use.  After Nov. 10, the focus will be on fixing high impact bugs turned up by those of you testing the release candidate. I suspect 2.7 will be ready for final release by the end of November.  A specific date will be set as we progress through the public beta cycle and get a feel for how solid the release is.

Get WordPress 2.7 Beta 1.