Upgraded to WordPress 2.7

miahz.com is now running the Beta 2 version of WordPress 2.7.

The new dashboard and admin interface is a huge improvement. So much information, yet easy on the eyes. It all feels much more organized and structured. Haven’t checked out any other upgraded functionality, but the visual redesign in /wp-admin/ is well-done.


[Clever "trailer" previewing the new admin features.]

Ironically, i used the WordPress Automatic upgrade plugin to make the jump from 2.6.1 to 2.7b2 as i have for previous upgrades, because i hate having to download, unpack, and upload zip files. The irony being that WordPress 2.7 now includes automatic core updating, so from here on out it should be a one-click affair; this will likely be the last time i will have used WAU. In order to hack WAU to install the Beta 2 pre-release version i used WordPress’ built-in Plugin Editor to change the coded download link from http://wordpress.org/latest.zip to http://wordpress.org/wordpress-2.7-beta2.zip. Just replace that URL on the line with $downloadURL, save, then proceed as usual.

WordPress' "Permalink structure updated" notification.

I also changed my permalink structure to the cleaner /year/month/slug/ format (i originally used /log/year/month/day/slug/). So this post’s link is: http://miahz.com/2008/11/upgraded-to-wordpress-27/. Old links automatically redirect to the new addresses. No plugins necessary.

  1. Hi, i have tried your way with the release RC1 but nothing happened i still can’t upgrade …

  2. Are you getting an error message? Which URL did you use when you edited the plugin?

    For RC1 you should have replaced “http://wordpress.org/latest.zip” with “http://wordpress.org/wordpress-2.7-RC1.zip”.

  3. There is no any error message, i have replaces the URL “http://wordpress.org/latest.zip” with “http://wordpress.org/wordpress-2.7-RC1.zip” at the line with $downloadURL

    Maybe this is happening because of the blog language , i will try it with the English version of the blog

  4. Hmm, i’m not sure what’s going on without more info. Just to be clear – i already had the AutoUpgrade plugin installed, and had used it previously for regular WordPress upgrades, before i decided to try “hacking” it for the 2.7 prerelease.

  5. Also nothing happened even with the link http://wordpress.org/wordpress-2.7-beta2.zip

    I don’t know what is wrong…

  6. Yeah, i think the problem is probably with the Upgrade plugin, not the link you’re using.

    What version of WordPress is currently on your site?

  7. the latest stable one v2.6.5

  8. Mena,

    Since you are on the most recent stable the plugin is checking to see if you are updated and once it sees that you are it does nothing. I am guessing that Jerimiah was not current when he made his hack.

    I had to do one additional hack. Find this line 1/3 the way down:

    if( ! $prelimCheck->runUpgradeRequiredCheck()) {

    It will have the only occurrence of runUpgradeRequiredCheck() so you can just search for that.

    Then remove the exclamation point. This reverses the logic and makes it only run the update if you are on the most current stable version :)

  9. Thanks for the tip, Luke. You’re right, i was several point-updates behind the latest: 2.6.1 at the time. I had no idea that might make a difference. Were you able to use this method yourself with your additional hack? I should update the post to include that info.

    Mena, let us know if you get it working.

  10. My friend helped me to update it manually but i didn’t update the English version of the blog yet, i will try your way with it and will tell you the result

  11. Yes, the hack worked great. I would recommend disabling all other plugins first though. I had several that did not work in 2.7 and caused a bit of trouble.

  12. I have done it, it’s working fine and I’m now using the latest version of word press 2.7 RC2

    i guess I’m going to disable all the plug-ins i have right now because i have problem with the sidebar [ It's not there ]

  13. oh yeah, now it’s there, now i have to know what plug-in caused that …

  1. No trackbacks yet.