WordPress 3.3.1 Fixes Security Exploit

WordPress 3.3.1 was released last night and it addresses an important security issue discovered in WordPress 3.3. Along with the security fix, the release also fixes 15 issues that are outlined here. After I upgraded the Tavern website, I was a bit confused to see a number of things that were listed under the What’s New section. Most of the features outlined were introduced in WordPress 3.3, not 3.3.1.

WordPress 3.3.1 Whats New

When questioning this move on Twitter, Evansolomon responded with the following:

evansolomon @wptavern Full feature list is more useful for anyone using < 3.3. As 3.3 is still very new, good case that less accurate = more useful here

I guess that makes sense but it still throws me for a loop a little bit because it looks like those features were added with 3.3.1, not with 3.3. So the question I have for you is, do you think the What’s New section should be strict in only listing what’s new with that specific version or should other features from previous versions be shown as well?

8 Comments


  1. Q: Do you think the What’s New section should be strict in only listing what’s new with that specific version or should other features from previous versions be shown as well?

    A: Only the specific version unless noted which version it implies to. After the break of Maintenance and Security Release it could say something like

    Introduced in WordPress 3.3

    Report


  2. Yeah, that kinda threw me too! Maybe give a list of new features sor the last ‘so many’ releases? Or since the last major release or something…. Have em sorted in rev. chrono order Like:
    What’s new
    This version (3.3.1)
    – stuff

    Version 3.3
    – original major stuff

    Report


  3. I think the major features should always be shown somewhere (i.e. for 3.3, 3.4 etc.), with updates and security fixes for smaller point releases added above.

    I also found it a bit weird that more 3.3.1 updates were not visible. I didn’t mind the 3.3 stuff still being there but the smaller point release updates need to be included too.

    As a newbie user, if you were to install WordPress for the first time and it was 3.3.1 and only saw the smaller point release updates then all the 3.3 features would be hidden – which is one good reason for still including them.

    Report


  4. I see what you’re on about, but as it’s like a security update, not UI or a substantial change, someone downloading 3.3.X for the first time would only be greeted with security updates in ‘What’s new’, and nothing else.

    Report


  5. The “Welcome”, “What’s New” page was certainly a nice touch in v3.3, tho it did occur to me that it might not ‘wear’ as well as hoped.

    In the case of v3.3.1, I took it that the Dev crew had – ‘natch – been running butts to a frazzle, stomping out all the (usual, predictable) spot-fires, and now they just needed to tie up the loose ends and get the new package out the door – ASAP.

    So … the loving editing that went into making “Welcome v1.0” so nice & smooth … became just a partial edit to quickly-insert what had to happen, for WP_v3.3.1.

    It might be, “Welcome” et al should be on the Dot Org site, and our Admin should just have a link, instead of another installed panel. Then, editing of it can be on-going.

    Report


  6. @Ted Clayton

    It might be, “Welcome” et al should be on the Dot Org site, and our Admin should just have a link, instead of another installed panel. Then, editing of it can be on-going.

    or brought in by iframes or whatever else.

    Report

Comments are closed.