Generally this is what I always do when my status report tells me that there are newer versions of modules available:
1 - Site maintenance mode
2 - Backup site and database
3 - Remove - rm -fr xxxxxx modules from my modules directory
4 - Download and then unpack the newer versions into the modules directory
5 - Run update.php
How do you know when you have to run update.php though? I notice sometimes that it says no database updates are required after I update my modules.
When I tried upgrading one module - I had a fatal error occur during the update.php process. I reverted and re-installed the last RC of that module and then manually selected the latest update v. 6000 for that module. Everything seems to be fine now? Am I cool? :)
Comments
Looks like. Keep checking
Looks like. Keep checking your Error logs for any signs of problems.
Switch to 6.4—module upgrading here is much simpler (as easy as updating your anti virus software).
To migrate 5.x to 6.x, I have written a couple of PHP scripts that can be found here: http://drupal.org/node/308187
Yes that looks a good
Yes that looks a good process.
>How do you know when you have to run update.php though? I notice sometimes that it says no database updates are required after I update my modules.
That's the easiest way of finding out.
>manually selected the latest update v. 6000 for that module
You shouldn't ever have to select which update(s) to run (in fact there is an issue open to remove this facility) since if Drupal is unable to select the right update then either your site is already broke or else the module's .install file is. If Drupal said that no updates were needed then you have basically run the update routine 6000 on a site that didn't need it. Depending on what the update 6000 does this may or may not have caused a problem. If you can't see any errors then chances are that all is well. HAving said that, bear in mind that the RC version of whichever module it is may have one or two bugs.
gpk
----
www.alexoria.co.uk
gpk
----
www.alexoria.co.uk
is there a section in the documentation about updating modules?
I recently had to update modules on several sites, and this is the only guidance that I could locate for the process. It seems like it should definitely be included, very explicitly in the documentation. For example, I was not sure if I needed to disable the modules before updating.
Otherwise, thanks for the summary! It is succinct and exactly what I needed.
General rule is to disable
General rule is to disable contrib modules when doing a major version update (e.g. 5.x to 6.x) but not usually necessary for a minor update (e.g. 6.1 to 6.4). http://drupal.org/upgrade .. check out the videos.
gpk
----
www.alexoria.co.uk