By tpainton on

I just got done searching the forums and found really nothing that would help, aside from Drush, which isn't an option when several, actually all, off my sites do not allow me to have shell access.

I am talking about the updrade to 6.19 which really needs to take place ASAP and some of my sites have many modules..

What a pain. I actually have to take a pen, write down what modules are activated, go through and then deactivate them. Many require other be inactivated first, then a refresh, then go back.

This results in deactivating more modules, and of course writing down on paper with a pen, those modules.. Inevitably I forget to write down a module and I learn about it the next day when a customer says, "Hey I was trying to check out and there is no cart button!" ARGH. It appears I forgot about that module!!

The process now takes me about an hour for 5-6 websites. I am glad I don't have 10-20.

This has been addressed and seems to pushed to D7 or written off as "how long can it possibly take?"

It seems that simple module could take a snapshot of the modules enabled, disable them, and then reinable them after the updrade.. AHHH THAT WOULD BE BLISS.

Drush appears to do this, but again, I don't have shell, and I love my Rackspace accounts, so I don't want to move.

How do other people address this? Is there a better way to speed this process and make sure all important modules are activated?

⋅ Categories: Drupal 6.x

Comments

heine’s picture

heine commented

For minor version upgrades where settings.php has not changed:

  1. Backup all files making up the site (you will need this!).
  2. Backup site database.
  3. Remove everything from the site root (including subdirectories).
  4. Copy the contents of the release.tar.gz into the site root.
  5. Copy the sites directory from the site backup into the site root.
  6. Run update.php

Sometimes additional steps are required before you run update.php;
- if your files directory is not in sites/, also copy it back from the backup.
- if a module added files to misc/, make sure to copy them over as well.
- if you modified .htaccess, check if the file has changed in the update and apply those changes.

tpainton’s picture

tpainton commented

great. Error 500 following this rec. Note I did not uninstall modules as you did not recommend it. So, now I am restoring from back up. I knew this was going to take all day.

heine’s picture

heine commented

Error 500 caused by what? Check the php / apache error logs. Perhaps your Apache conf forbids the use of certain directives in .htaccess.

jtjones23’s picture

jtjones23 commented

Minor upgrades take me about 5 minutes. See http://drupal.org/node/360468#comment-1206797

Michael Fuchs’s picture

Michael Fuchs commented

Yes: Before you upgrade, go to your Modules page, which will show all your enabled modules. Save the page, somewhere local.

Turn your modules off, do your upgrades, go back to modules.

Open up the saved version, side-by-side with the live version, and turn all the ones that should be on back on.

Et voila tout.

tpainton’s picture

tpainton commented

Great idea. It just seems like somethign that would be simple to automate.