WordPress 3.0.1 Released

July 29th, 2010
WordPress, WordPress News

WordPress 3.0.1 has been officially released. This release fixes 55 minor issues, including a frequently reported export error and an incompatibility with PHP 5.0.5.

The upgrade should be available for most of you from your Dashboard. If you don’t see the announcement, go to Dashboard/Updates. If you encounter any trouble with the automated updater, try deactivating your plugins before reinitiating the update. As is accustomed with Murphy and his fabled law, a manual upgrade many be required, but it shouldn’t take too long.

If you need help, please submit your request to the WordPress Support Forums.




  1. Richard Hay (14 comments.) says:

    James – thanks for the news on this. Welcome to WLTC as well!

  2. Andrew Nacin (11 comments.) says:

    “an issue where logged in users could see trashed posts belonging to other authors” was WordPress 2.9.2, which is the Codex page we duplicated. I’ve removed the reference from the Codex.

  3. Nicolas (25 comments.) says:

    So I had an automatic upgrade fail and then decided to quickly do it the old school way. Now I have a “warning” in the back-end telling that I do have to redo the upgrade because the automatic one failed. Do I really have to do it again to make this message go away?

  4. sk says:

    I really wished they would fix the editor bug that came with WP3.0. If there are multiple writers and editors working in the dashboard, it no longer properly shows “Someone is currently editing this post” warning in red at the top.

    We’ve had a bunch of accidental overwrites and loss of text due to that new bug that wasn’t there in the 2.x series.

    • Andrew Nacin (11 comments.) says:

      This is the first report I’ve seen of this. And, for what it’s worth, it works fine for me, and even prevented us from stomping on each others’ changes for the 3.0.1 announcement post this afternoon.

      Not sure if it’s worthy of a bug report, but perhaps start in the support forums and go from there?

  5. Nicholas Teo (37 comments.) says:

    Thanks for this information, I just upgraded to 3.0.1.

  6. Khaled riyadh (4 comments.) says:

    did u face any problem till now ? People are telling me to wait and let others test.. But m too desperate.. Should I go ahead download it ?

    • James Huff (62 comments.) says:

      3.0.1 fixed most of the bugs reported in 3.0, and it didn’t introduce any new features, so it shouldn’t have introduced any new bugs. I’d say that it’s safe to upgrade now.

  7. Web (1 comments.) says:

    This release is good for people that are having some issues with 3.0. Hope they have been fixed. I actually am still on 2.9.2 :)

  8. Aj (9 comments.) says:

    Yup – Just Updated – All 20+ of my sites…Thank You Auto-Upgrader.

  9. Sumon (1 comments.) says:

    Many many thanks to WordPress Team for Release New Version.

  10. Atlanta Plumber (1 comments.) says:

    I think it is better to always stay updated on wordpress to keep the hackers from ripping your site apart with some minor flaw they may find.I migrated from oomla to wordpress and love it because of the auto-upgrader

  11. Nasif (3 comments.) says:

    Does thesis 1.7 work well with wordpress 3.0.1 ? There was a problem with wordpress 3.0, don’t whether the problem still exist in the newer version.

  12. Andrew @ Blogging Guide (123 comments.) says:

    Thanks for the info. Will be upgrading now.

  13. Hikari (26 comments.) says:

    My bug report was in 3.0.1 and was moved away, it wasn’t fixed ;_;

  14. Kimi (2 comments.) says:

    Yes, i did upgrade without any problems, love it!

    Also the smart video bug which i had in earlier version, now works again..

    WP rocks! ;)

  15. Grischa (1 comments.) says:

    Hey. Good to know about the update! I’m always having problems during the update. And afterwards I have to do everything manually again. I think my webhost has strong restrictions. Do you recommend to update wordpress? I think it’s not really necessary at the moment, because it fixed no security related issues. Never touch a running system…

  16. Photovoltaique (1 comments.) says:

    Thanks for the news, but i’m still working with WP 2.9.2, got some troubles with WP 3.0

    i actually don’t know how to fix it

  17. weevie833 (1 comments.) says:

    Couple bugs I noticed after upgrading to 3.0.1, though I haven’t checked to see if they’d been resolved, nor whether they were theme-specific. Maybe someone else will have the same trouble with better details:

    – Changing page parent in Quick Edit causes total edit mode failure and it switches to an empty page listing. Refreshing the Page menu returns to the normal listing. Changing page parent can only be done on full edit screen

    – Creating more than four Custom Menus causes main menu failure. I registered 9 menus in Functions, pasted the requisite code in each custom page template (such as, page-about.php). I then created the first three or four (can’t remember exactly) custom menus, but as soon as I went beyond that, the main menu only showed the fourth custom menu, not the designated main menu. This was no cure for this but to downgrade back to 3.0 with a total fresh install and a lot of re-doing work (tried turning off plugins, etc.). I was using Graph Paper Press’ Widescreen theme. There were no 3-level sub-navs in any of the menus.

    Again, hard to say the exact cause of these, but FYI. – Steve

  18. Ayesha (1 comments.) says:

    I upgraded to 3.0.1 today & now am having issues with my images. I am using the Twenty Ten theme. The first issue is when I upload multiple images together as an attachment page, clicking on the thumbnail only displays the portrait image correctly. When I click the thumbnails for landscape images they are cropped like the header. The other issue is when I select a featured image, it is not displaying. I had a blog prior to this new one & prior to the upgrade & it all worked well & still does, just not the new post.

  19. Pet (1 comments.) says:

    I was a bit nervus abut updating as I am just getting the hang of WordPress generally. No problems so far since upgrading my sites.

  20. Nathan Williams (2 comments.) says:

    Upgraded today. Had to do it manually. Thanks for the tip Andrew. Works fine now.

  21. Lars Hilse (2 comments.) says:

    When I updated I almost got a heart attack because some plugin failed to integrated and the whole blog was down, thus my entire website.

    Hard to imagine that there is no better way to ensuring operation even when one part of the entire system fails to work.

  22. Ed (2 comments.) says:

    Anyone else keep running into failed Automatic upgrades? It always seems to be over some css file that can’t be added. Anyone know of a file permission issue that needs to be addressed? Or any other reason this would continue to happen with every upgrade I try?

    Self Installed, WordPress 3.0 to 3.0.1, on both VPS and dedi servers. Not sure what the problem is.

  23. SenseiMattKlein (14 comments.) says:

    I’m with Nasif above. Heard there are some issues with thesis so I’m waiting for Thesis to announce that it is compatible. Maybe an update soon?

Obviously Powered by WordPress. © 2003-2013

page counter