You are hereBeware of folder precedence for Drupal modules

Beware of folder precedence for Drupal modules

It's important to keep Drupal modules up to date.  Drupal 6 is seeing a steady stream of revision releases now as bugs are fixed and security issues addressed.  But a subtle issue with module loading precedence  can cost time on what seems like a simple enough task. When updating an installation with any traffic at all, be sure to go through the step of putting the site in Maintenance mode before FTPing the replacement modules so that you don't get access to your DB with code that does not match the DB Schema.   Upload the newer module to your server and be sure to run update.php after to make certain any schema adjustments are made as soon as the file transfer is complete.   Then run cron.php to refresh Drupal's temporal awareness and check status for available updates. Sounds redundant I know, but every once in a while I've installed a new module revision only to find that as soon as I was finished, a different module needed revision. It's also a due diligence step to confirm the revision took place.   Every once in a while I am surprised and a bit frustrated to see that, although I clearly have installed the latest revision, a check of available updates shows that the module I just uploaded to the server still needs updating.   I've driven myself to distraction more than once on this issue until I remember that Drupal follows a process to discover modules which can get confused if there is more than one copy of a given module in the search tree.   A good example is when I decided to include inside sites/all/modules a directory named CCKmodules which holds all the little modules that provide CCK field types.   I was updating one of those, but no matter how many times I uploaded the revision, Status kept insisting I still needed to replace the older version.   That is because I had an older version out in the modules directory that was being loaded.   The solution if you can't get a revision to happen is to do a search for folders with the same name as your module and if you find more than one in the installation, remove the older one and make sure there is only the latest version available.