By gohanman on

I was updating several out of date modules today and ran into an issue I've never seen before: Drupal absolutely refuses to notice that the module was updated. Here's what I did:

cd sites/all/modules
mv cck cck.backup
tar xzf cck-6.x-2.6.tar.gz

Put site in maintenance mode
Run update.php

No database updates are listed for the cck sub-modules I have enabled, so update.php doesn't really *do* anything. When I'm done, Drupal claims CCK is version 6.x-2.5 and needs updates, but CCK's .info file claims it's version 6.x-2.6.

Oddly, this exact procedure worked perfectly for every other module that needed updates, including other modules that had no database changes.

What am I missing here? Is there some way I can force Drupal to re-check what module versions are present?

⋅ Categories: Drupal 6.x

Comments

ezraw’s picture

ezraw commented

Move the backup directory out of the sites/all/modules directory and see if that makes a difference.

Are you running multisite by any chance?

Ezra Wolfe
DLC Solutions
EthosCE

gohanman’s picture

gohanman commented

Getting rid of cck.backup did the trick. Thanks.

robroberts’s picture

robroberts commented

I have this same problem, except I don't have a backup in the same directory. I am using multiple sites in the sites directory, and putting CCK 6.x-2.6 and FCKeditor update files 6.x-2.0 in their respective directories (under sites/all/modules). I'm still using Drupal 6.14, but every other update done last night (Views, Ubercart, Messaging and Zen) updated correctly on all 3 sites in the multisite setup.
Anyone have ideas?