Everyone knows by now that WordPress 2.7 is packed with new features. Now that it’s available (almost 600,000 downloads as I write this!), it’s time to start working on 2.8. There were dozens of things that got tabled during 2.7 due to time constraints, and there are a lot of high-rated features in the Ideas forum, so there are a lot of potential features under consideration.
Right now, the lead developers are thinking the top priorities for 2.8 will be widget management, theme browser/installer and performance upgrades. The rest of the development time will be taken up with bug tickets and additional features/enhancements from a prioritized list. To that end, we’ve posted a new survey for you to help us prioritize features for 2.8. The list pulls from the developers’ “2.7 leftovers” list as well as the most popular features from the Ideas forum. Just rank each feature and tell us your top pick (up to three). You also have the option of adding comments or additional suggestions, but this is not mandatory. For your response to count, you must rank all of the features in the list. The survey has only one page.
Note that media features are not included in this list as we will be posting a separate survey for media-specific features soon.
Cast your votes any time this week, but as always the sooner the better. This survey will close at noon on December 31, 2008 UTC.
In the new year, we will be reviving scheduled IRC developer chats, where the lead developers will discuss the week’s progress on feature development, providing opportunities for people to ask questions or make suggestions. These will be held early in the day on Wednesdays (U.S. Wednesday), and the specific time will be posted here on the development blog once it’s been finalized.
As a related aside, we spent a significant amount of time during 2.7 development sifting through Trac tickets that really shouldn’t have been there. Feature ideas and requests do not belong in Trac, they belong in the Ideas forum. Please reserve Trac for reporting bugs and things that need fixing (typos, code enhancements, etc.). If you are asking for a new UI, a new feature, or a new approach to coding something, that’s not an enhancement, it’s a new feature. New features will be entered into Trac by developers once it has been determined that the feature should be included in core. To help speed up development, moving forward we will close Trac tickets that are actually feature requests, with the comment that they should be posted in the Ideas forum instead. Please help the developers maximize their time by following this guideline.
The first thing you’ll notice about 2.7 is its new interface. From the top down, we’ve listened to your feedback and thought deeply about the design and the result is a WordPress that’s just plain faster. Nearly every task you do on your blog will take fewer clicks and be faster in 2.7 than it did in a previous version. (Download it now, or read on for more.)
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):
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):
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.
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.
Of course if you were already testing 2.7, you can just use the built-in core updater (Tools > Upgrade) to download and install RC2 for you (and later upgrade you to the final release when it’s available) but if not you can use the download link above.
We feel this release is pretty much exactly what we’re going to ship as 2.7, barring any final bugs or polish tweaks that you report or we find.
With the release of RC1, we’re in the final leg of development before the release of 2.7. 280 commits since beta 3 have polished the new admin UI (including new menu icons created by the winners of our icon design contest) and fixed all known blocker bugs.
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.
The security issue is an XSS exploit discovered by Jeremias Reith that fortunately only affects IP-based virtual servers running on Apache 2.x. If you are interested only in the security fix, copy wp-includes/feed.php and wp-includes/version.php from the 2.6.5 release package.
2.6.5 contains three other small fixes in addition to the XSS fix. The first prevents accidentally saving post meta information to a revision. The second prevents XML-RPC from fetching incorrect post types. The third adds some user ID sanitization during bulk delete requests. For a list of changed files, consult the full changeset between 2.6.3 and 2.6.5.
Note that we are skipping version 2.6.4 and jumping from 2.6.3 to 2.6.5 to avoid confusion with a fake 2.6.4 release that made the rounds. There is not and never will be a version 2.6.4.
The community has voted, and the votes have been tallied. The winner of Project Icon, with 35% of the votes, is Entry ID “BD,” otherwise known as Ben Dunkle. Congratulations, Ben! The runner-up was VS, otherwise known as Verena Segert, so we’ll be attaching that set to the alternate color palette that is selectable from the profile screen. As we prepare for RC1, Ben and Verena will be revising a couple of their icons so that both sets will use the same metaphors, creating the colored “on” states, and creating the larger size of each icon for use in the h2 screen headers. We are very grateful to have had the opportunity to select from so many great options, and would like to express again our appreciation for all the designers who participated in the contest. Thanks also to the more than 3700 people who completed the voting survey and took the time to weigh on on the individual icon sets.
Q.18 Which one of the sets do you think we should use as a basis for the 2.7 icons?
# of votes
% of votes
The wide lead of BD and VS made it clear that voters had a clear preference for these sets.
Q.20 If you could choose a runner-up, which would you choose?
# of votes
% of votes
Question 20 was not mandatory, so a few hundred people skipped it, but the responses we did get (3366 of them) reinforced the fact that the two most popular sets were also the most popular 2nd choices, which made the decision of the judges to go with the popular vote an easy one (take that, electoral college!).
A few of the individual icon metaphors also had a significant lead over the other choices. Dashboard: 1333 voters (40%) chose a house as the best metaphor. We agree, so both Ben and Verena will be replacing their Dashboard icons.
Media: 2097 voters (65%) chose the combination camera + musical note icon, which was part of Ben’s set. We also really loved it, and Verena will amend her media icon to incorporate this idea.
Plugins: 1682 voters (53%) selected the outlet plug metaphor, which both Ben and Verena used in their sets.
Tools: 1581 voters (49%) liked the combination of two tools better than anything else, so Ben and Verena will try this approach.
So those are the results, and soon you’ll see the new icons coming to a 2.7 installation near you.
Need another look at the entries to remember which one you liked best? Here are some reminder images, as well as the identity of each set’s creator.
BD was Ben Dunkle, a designer, professor and artist from upstate/western New York State. In case you’ve already forgotten, Ben’s icon set is the winner of Project Icon and will become the default icon set after a few minor changes.
VS was Verena Segert, our runner-up, a designer from Germany who presented sets in both grayscale and blue. Her blue icons received more specific voter comments than the gray ones, so we’re planning the second color palette to be in shades of blue so that we can use the blue icon set.
GB was Guillaume Berry, a designer from France who submitted two sets in the same style in order to propose a couple of different metaphors. One of his sets came in third while the other came in last, but whether you only look at the higher scoring set or you combine their votes, Guillaume had the next highest percentage of votes, and many people liked the metaphors he used for various icons. In fact, given the enthusiasm of the community for Guillaume’s icons, we think a great plugin would be one that would allow the user to upload the icon set of their choice. Any volunteers?
OSD was the Open Source Design class at Parson’s in New york City, taught by Mushon Zer-Aviv and consisting of students Alexandra Zsigmond, Ed Nacional, Karen Messing, Khurram Bajwa, Leonie Leibenfrost. Teacher and students worked together to determine their metaphors and visual style.
LS was Luke Smith, a designer from Iowa who specializes in icons among his other design pursuits.
If you need to hire an icon designer any time soon, we highly recommend our Project Icon contestants, who all delivered great work in a very short timeframe. It was great to work with all of them, even for such a short assignment.
So, to sum up:
The winning icon sets by Ben Dunkle and Verena Segert will be incorporated into WordPress 2.7 RC1.
Someone should write a plugin that would allow anyone to upload a custom icon set (I bet the other contestants could be convinced to release their icon sets for such a purpose).
2.7 is still trucking away, but we can always use help with patches, especially for IE6! (I know, that wasn’t in the main post, but it’s true, so hmph)
Thanks again to everyone who participated in this experiment, and we hope you enjoyed it as much as we did. And congratulations again to Ben and Verena!
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.
Earlier in the beta period, we put out a call here on the development blog for designers in the WordPress community who might be interested in designing custom icons for the 2.7 admin interface. Over a dozen icon designers from around the world responded, so rather than choose just one, we decided to turn the icon design assignment into a contest so that more people could participate and the community could have a vote in what the new icons should look like.
Once we decided to go with a contest format instead of a single-designer gig, about half the original volunteers changed their minds. The remaining designers each submitted two icons (Posts, Links) in their proposed style. At this stage a couple of designers were thanked for their submissions but eliminated from the competition because their icons were considered too far afield from the WordPress visual style. The remaining designers were given feedback on the icons they had submitted and given about a week to complete the icon set for the menu as well as the list/excerpt icons that are shown on the Edit Posts screen. All but one of these designers finished a complete set, giving us five sets in total.
So now we need to choose a direction. For each of the icon sets, we’ll show you the set itself, the designer’s introduction, and some feedback from the lead developers. After you’ve reviewed all five, place your vote for the set you think has the visual style that is the most suitable for WordPress 2.7. This will be followed by additional votes on specific icons, so if you like the specific image used in one set but like the style of another, you can vote to change the metaphor for a given icon. You’ll also be able to leave general feedback throughout the voting process. When voting has concluded, we’ll review the comments and the votes, and will declare a winner.
Things to bear in mind when making your selections:
A week is not a long time to create 13 icons. The winning set will undergo a revision to be refined, and some icons may be substituted. We asked for all icons in grayscale for the contest. An “on” state and a larger size for screen headers will be designed by the winner. It seemed like too much work to have everyone do multiple states for so many icons.
Ready? Go and take the icon survey.(The survey has now been closed.) Voting will remain open for 48 hours from the time of this post to allow people from all time zones a chance to participate before we close the survey and make a decision (since we’d like to include the new icons in Beta 3).
A Note Regarding the 2.7 Release Date:
As we approach Beta 3, bug tickets continue to be added to Trac, the pain of making things look good in IE6 continues to be felt, and the need to improve accessibility looms. If you love WordPress, are a decent coder, and want to contribute like these icon designers contributed, please consider contributing a patch to help with one of these efforts. Jump right in on current Trac tickets, or pop into the #wordpress-dev IRC channel to ask what to do.
Welcome to the first post of the first blog on the wordpress.org domain dedicated solely to WordPress MU (WPMU).
Sure, this isn’t most likely going to see the light of day for some time, but it’s important to have it here, don’t you think?
Anyway, down to business…
The problem, as it stands is that:
There isn’t enough centralized support material and communication for WPMU
This is pretty much down to:
There’s a lot of duplication between WP and WPMU resources, with 98% of regular WP codex stuff applying to WPMU
There aren’t as many WPMU users / devs… it’s just not as popular because fewer people need it
And when they do need it, it’s usually for other people rather than themselves – to paraphrase Douglas Adams, I’ll spend days working out how to save myself a minute once a fortnight, but not much bother with stuff that’ll save other people weeks (OK, the last bit was me
Let’s face it, we’re an offshoot, a kinda more complicated sibling
So, we’re not going to manage to get around this by mimicking what’s happened for WP – we’ve been doing that for a while, without any luck.
So, what I propose is this:
WPMU (via this site) exchanges linkworthy respect and credit for knowledgeable people penning articles about aspects of WPMU here, as Contributors and Authors
Those articles are, as they come in, organized a la faq.wordpress.com an dmaintained by their respective authors (with assistance from a set of editors – hopefully promoted contributors / authors)
That is then integrated into the forums and the forums are integrated into this, creating two places where there’s a great deal of good WPMU knowledge
And that we ditch:
The WPMU codex – it’s not used, no-one cares, it just give off a bad smell about WPMU an dcan be replaced by a good idex of materials here
Trying to support WPMU outside of the forums and posts here – this gives us some good focus
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
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.