how to upgrade from 5.x to 6.x
Hi, I'm asking this on question to both Devel and Docs because I'm about to make an "upgrading" screencast and want to be sure that I'm using the best method. In our handbook[1] we tell people that before the upgrade they should "Turn off (but do not uninstall) all modules that are not core modules" I've done that a few times and it always threw various errors when I then installed the updated versions of the contrib modules. I then started to follow steps more like: 1. Download the new version (i.e. 6.x) 2. Download the 6.x compatible version of all my contribs (fix or remove the ones that haven't been upgraded) 3. Install the new core and contrib modules 4. Run update.php which will do all of core and contrib at the same time which, in my experience, causes fewer errors In discussion last night chx mentioned that the reason we tell people to disable the contrib modules is to prevent bootstrap.inc from calling a function that no longer exists and thus locking you out of a site. I think that is not a problem as long as you do my steps 2/3. Does anyone have a concrete, repeatable, simple example of why doing it my way is worse than the way in the handbook? I think this might be a relic of the update process of years gone by that we can now forget, which would be nice since I think it simplifies the process. Regards, Greg [1] http://drupal.org/upgrade/preparing-the-site -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
On Jan 18, 2008, at 5:32 AM, Greg Knaddison wrote:
"Turn off (but do not uninstall) all modules that are not core modules"
Note: for update_status 5.x -> update.module 6.x, the recommended upgrade path is to disable *and* uninstall update_status 5.x before starting the upgrade, or people will be left with stale variables and tables in their DB which there's no automated way to clean up. We need to start getting the word out about this, or we need to put code into update.install to seek out this stale data and destroy it when you install update.module for the first time. If we go the documentation route, it'd be nice if installation screencasts like yours mentioned it. Thanks, -Derek
Quoting Greg Knaddison <greg@pingvox.com>:
1. Download the new version (i.e. 6.x) 2. Download the 6.x compatible version of all my contribs (fix or remove the ones that haven't been upgraded) 3. Install the new core and contrib modules 4. Run update.php which will do all of core and contrib at the same time which, in my experience, causes fewer errors
This sounds logical to me and basically how I've done my updates. The .install of each module core or contrib should provide updates to stale variables or anything else that it needs to upgrade. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
On Jan 18, 2008 2:32 PM, Greg Knaddison <greg@pingvox.com> wrote:
In our handbook[1] we tell people that before the upgrade they should
"Turn off (but do not uninstall) all modules that are not core modules"
Does anyone have a concrete, repeatable, simple example of why doing it my way is worse than the way in the handbook? I think this might be a relic of the update process of years gone by that we can now forget, which would be nice since I think it simplifies the process.
I think this is stated so that update errors are easier and quicker to spot. The core upgrade is expected to be much more tested compared to contrib upgrade paths. But it might not work out. And then if it does, AFAIR, people are told to update modules one by one, to be able to act on errors which come up. Doing your way, seeing a long update list run by with some stuff broken means you need to resort to the suggested method anyway. Personally, I use your way by the way, and I also do crazy version hopping, but I always run through the upgrade lots of times, solving data consistency issues, hammering the upgrade path of my own modules and such on the way, to get to an error-less upgrade at the end. My way is not something I would suggest to people, as they are nervous enough with one upgrade pass, not to say running it 10-15 times :) Gabor
participants (4)
-
Derek Wright -
Earnie Boyd -
Greg Knaddison -
Gábor Hojtsy