I just recently tried to upgrade a Drupal 6.16 installation to the recommended 6.22. It fell in a crumpled heap! I did the upgrade using drush and it produced loads of warning messages about disabled modules because the 'module wasn't compatible with the new version' and also did some database changes which I'm pretty certain was what broke the system completely.
I have reverted to 6.16 and restored the database and all is well now, but I'm a bit unsure how to proceed as it feels as if I really should do the security upgrades.
I'm afraid I lost the output from drush where all the warning messages were shown because I just wanted to undo the mess.
I can possibly try again with (yet another) copy of the site and show the error messages here if that might help.
Chris G wrote:
I just recently tried to upgrade a Drupal 6.16 installation to the recommended 6.22. It fell in a crumpled heap! I did the upgrade using drush and it produced loads of warning messages about disabled modules because the 'module wasn't compatible with the new version' and also did some database changes which I'm pretty certain was what broke the system completely.
6.16 to 6.22 should be a matter of just doing the upgrade. You might need to disable modules and do the upgrade for them one by one.
I have reverted to 6.16 and restored the database and all is well now, but I'm a bit unsure how to proceed as it feels as if I really should do the security upgrades.
I'm afraid I lost the output from drush where all the warning messages were shown because I just wanted to undo the mess.
I've never used drush. I've always used the GUI. The warning messages though may have been stored in the watchdog table and might could have been viewed from the log report. But that is gone now since you've restored the DB.
I can possibly try again with (yet another) copy of the site and show the error messages here if that might help.
I suggest making a copy of your production to a development instance and give it a go there.
On 11/07/11 11:41 +0100, Chris G wrote:
I'm afraid I lost the output from drush where all the warning messages were shown because I just wanted to undo the mess.
That's to bad, it might have given us a clou what went wrong. You could record the shell session with
script -t 2>~/upgrade-drupal.time -a ~/upgrade-drupal.script
I can possibly try again with (yet another) copy of the site and show the error messages here if that might help.
I would try three different approaches:
a) Deactivate all unneeded modules, upgrade, then upgrade the modules one at a time and reactivate them. Run update.php after each step. b) Make incremential updates, 6.16->6.17...6.22 c) A combination of the above
Good luck Rolf
Rolf Kutz wrote:
b) Make incremential updates, 6.16->6.17...6.22
Unless otherwise noted this shouldn't be necessary between major versions. From d.o/upgrade we have:
Minor update procedure With a minor release update; such as from Drupal 6.1 to the latest Drupal 6.x version, you do not have to apply all the updates that have been released between the versions. You can jump directly from 6.1 to that version.
See http://drupal.org/node/3060/release for release notes.
Any time you upgrade any module, you may temporarily receive messages until you do the update.php. This is especially true if there are schema or theme changes. I don't know if there are any between 6.16 and 6.22. All the interim releases are still available on DO, so you can always go back and do smaller changes. I always test updates on a local copy of the site to make sure that, no matter how well tested, they don't break MY site. This is why I carefuly read the security announcements and don't run the Update module on my live sites.
Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Chris G
I just recently tried to upgrade a Drupal 6.16 installation to the recommended 6.22. It fell in a crumpled heap! I did the upgrade using drush and it produced loads of warning messages about disabled modules because the 'module wasn't compatible with the new version' and also did some database changes which I'm pretty certain was what broke the system completely.
It's generally a good idea to upgrade (update) all of the modules *before* you try the core upgrade.
Also, make sure that any of your development, alpha, or beta modules, actually end up at the right version. I don't know if it still does it (probably not), but in the past, drush would allow it to "update" to the non-development version of the module, which might be a significant downgrade. It's handling of versions has gotten a lot better in recent releases, so this may no longer be an issue, but you should still watch your versions.
Luke
On Mon, 11 Jul 2011, Ms. Nancy Wichmann wrote:
Any time you upgrade any module, you may temporarily receive messages until you do the update.php. This is especially true if there are schema or theme changes. I don't know if there are any between 6.16 and 6.22. All the interim releases are still available on DO, so you can always go back and do smaller changes. I always test updates on a local copy of the site to make sure that, no matter how well tested, they don't break MY site. This is why I carefuly read the security announcements and don't run the Update module on my live sites. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Chris G
I just recently tried to upgrade a Drupal 6.16 installation to the recommended 6.22. It fell in a crumpled heap! I did the upgrade using drush and it produced loads of warning messages about disabled modules because the 'module wasn't compatible with the new version' and also did some database changes which I'm pretty certain was what broke the system completely.
-
Chris G -
Earnie Boyd -
Luke -
Ms. Nancy Wichmann -
Rolf Kutz