The road to better upgrades

  1. Oceanwatcher


    I have seen parts of this in another post, but feel upgrades need a separate mention. This is also the same thoughts I aired some time ago in the forums.

    An easy way to upgrade is really needed. The five step upgrade might be easy for anyone that likes hacking code, but for any non-programmer that just want to install a blog and make sure it is updated and secure, the upgrading can seem scary.

    I think we all can agree that keeping all WordPress installations secure is a must. But with the current way to upgrade, a lot of people do not fix things until it is broken. And this has to be addressed.

    This would be the first thing on my list to do:

    Remove the subfolder in the zip file. This is a real annoyance. I never install WordPress in a subfolder as I run it as the main CMS on the sites where I use it. So upgrading is always a pain. Installing in a subfolder is again no problem if you are a programmer, can fix your .htaccess so nobody will notice it etc. But generally it is a bad idea to force this on people. If you want it in a subfolder, then create the subfolder of your choice and unzip it there. Most people do not have shell access to their hosting account. But many have cPanel. And in cPanel your only option is to unzip as is...

    The reason why I do not like unzipping and rezipping locally to get rid of the subfolder, is that I am hosting my websites on a Linux server, and doing anything to files on a windows PC locally tends to always break something...


    Make increment upgrades available (is this the right word?).


    Any older than 2.0 will have to upgrade to 2.0 first.

    This system is being used for Joomla at the moment and works great. Takes the whole problem out of upgrading. Just ftp the upgrade to your root installation and use cPanel to unzip it. Done. This of course requires the subfolder inside the .zip file to be removed.

    If we can only get to this level I am satisfied. It would be wonderful to go further, but getting this far would be a big leap forward.

    A good upgrade function inside WordPress would be to have a tool that check the WordPress.org server for new versions and alert you when you log on to the admin panel. It should compare the version you run with the latest version. Then have a button that download the upgrade and unzip it. Basically a little more automated version of the one above. This method only deals with WordPress files, so it does not matter what OS you are on.

    And the ultimate system would also include the plug-ins so everything is totally up to date.

    Posted: 11 years ago #
  2. Penina


    yes yes yes yes yes!!!!

    (in fact, I don't really care how it's done, as long as you make it really really easy)


    Posted: 10 years ago #
  3. jonimueller

    Movable Type used to do this as well. It was part of their installation documentation under the subheading Upgrades. There was a clear path you had to take to make sure everything migrated over smoothly.

    We do need that here, especially since there seems to be more and more distance between the legacy stable WP 2.0.11 and the latest and greatest. I myself am thinking of finally moving away from 2.0.11 to 2.5.1.

    Posted: 9 years ago #
  4. Jen
    Community Organizer

    Built-in upgrades is in core as of version 2.7.

    Posted: 8 years ago #

RSS feed for this topic

Topic Closed

This topic has been closed to new replies.

  • Rating

    102 Votes
  • Status

    This idea has been implemented