Upgrading Drupal modules
Upgrading modules is a more involved process than installing or removing modules. The steps should be followed closely, as all these steps are necessary to ensure the stability of your website.
Backup your Files and Database
Your website's database contains all of its content, as well as all of its settings and configuration. As such, any operation which modifies it could, although unlikely, be potentially damaging. Backing up your website's files will ensure that you can revert back to the point when things were working. We highly recommend you take steps to back it up before performing this procedure. More information about taking backups may be found at http://drupal.org/node/250790.
Update Module
Update capabilities are not automatically available in Drupal. To keep track of updates to your installed modules, you may want to install the Update module, which is located here: http://drupal.org/project/update_status
Check Module status
- The Update module can check your modules for updated status automatically to assist you with updates. It will provide you with download links and available versions. Once the Upgrade module is installed and enabled, you can reach a list of modules for update by either clicking on the “available updates” link on the main administration page or by going directly to
[sitename]/admin/logs/update. This page checks the current and the installed versions of modules, and will give a report on their status. This will allow easy updates without having to manually check each module installed in your website.

- In this example, the Views module is out of date. Any out-of-date module will be labeled in red, as shown above. We can upgrade this now.
Disable Module
You must first disable the module. Here is a tutorial that covers how to disable a module. Follow only part of the instructions listed there. Stop at the section labeled “Uninstalling a module” and only perform the first section of steps for disabling a module.
Reinstall Module
Next is reinstalling the module. The Update module also provides a download link which may be used to download the updated version instead of going to Drupal.org. Delete the outdated module's files and upload the new ones as if you were installing the module for the first time.
Run update.php
Update.php is a script that is used to maintain websites after upgrades. A new version of a module may change the structure of the database. This script adjusts the database to fit the updated module. As the database contains all of the content and the settings of your website, this is an essential step to ensure its continued operation.
- The update.php script can be called two different ways. You may go to the main administration page and click on the “update.php” link on the front page, or you may go directly to
[sitename]/update.phpin your browser.
- You will require admin privileges to perform this upgrade. The first account created on your site will have the required privileges.
- If you do not have the proper privileges, you will receive this screen. Either log in or follow the instructions on the page to perform the upgrade.
- Once you have the proper privileges, you will see this screen. Click on the “Select versions” link to expand the section.
- These dropdown boxes contain database updates specified by modules you have installed. If you are not developing your own module or troubleshooting, you should leave them alone and just click the “Update” button. The correct items should already be selected by default -- either “No updates available” if there have not been any database changes, or a number, which is simply an ID number of the database upgrade being applied.
- This next page may take a small amount of time to load, as the server is modifying your database. This page will display any errors that may have occurred during the process. If none have occurred, your module upgrade is complete!

Details
0. Test the new version of the module on your test site. (Goes without saying except when we don't have time.)
1. You must take your site offline during this process. If you have a multi-site installation, then that means all sites.
2. In Drupal 6, I believe Update status is in core and not a separate module
3. Under Reinstall modules, don't overlook
If you don't remove the old modules, as I have learned the hard way, Drupal may continue to report that you need the update.
Note: If the old module contains 4th party programs like FCKEditor, TinyMCE, etc. then removing the whole module means that you have to re-install/re-configure these other programs.
4. On a multi-site with multiple databases, I believe you have to run Update.php on each site.
Why is experience so painful?
__________________________________________________________________________________
Aweigh - not all who wander are lost.
Hey kayaker, you wrote 3.
Hey kayaker, you wrote
but the article says, that I'd have to stop following the steps where "Deinstalling" begins. Now I'm confused. Shall I deinstall the module after disabling or shall I delete the directory in /sites/all/modules manually?
Delete Outdated Module's Files
I'm only guessing here, but it may mean to make sure to simply not *copy* new module into old modules location which might leave a few of the old files hanging around in the module's folder.
When I install a new version of a module, I make sure to clear out the old one (usually by removing the module's folder) and then untar the new module. This insures I have nothing but the new version's code.