I just went through a bunch of updates on my site, including updating the core Drupal (to 6.19) and many modules that I had let get out of date.

After updating everything, I now get two modules that do not seem to have properly registered their updates: FileField and ImageField. Both of these appear in the available updates page with version "6.x-3.1", and the recommended version "6.x-3.7". I have definitely replaced these modules with the latest code, and ran the update for them. However, either the update wasn't applied, or there is something incomplete somewhere that is causing my site to still flag these as the older version requiring updates.

Any idea where I should look to fix this?

Comments

mgleahy’s picture

mgleahy commented

I should note, as similar issue like this came up in this issue: http://drupal.org/node/455716

However, the outcome from that issue doesn't provide me with a clear path forward.

quicksketch’s picture

quicksketch
he/him
commented

Thanks for search, though I'm sure I've answered this question several times before. You probably have multiple copies of FileField within your Drupal directory. Check your "system" database table and find the row for filefield, check the filepath. That's the version of FileField that is being used, which is probably still the 3.1 version and not the one you've uploaded. Delete the old version.

mgleahy’s picture

mgleahy commented

Ok...that was it.

In my DB, select * from system where name = 'filefield'; revealed the following:


                          filename                           |   name    |  type  | status | throttle | bootstrap | schema_version | weight |                                                                                                                                                           info                                                                                                                                                           | owner 
-------------------------------------------------------------+-----------+--------+--------+----------+-----------+----------------+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------
 sites/all/modules/downgrades/filefield/filefield.module | filefield | module |      1 |        0 |         0 |           6104 |      0 | a:10:{s:4:"name";s:9:"FileField";s:11:"description";s:26:"Defines a file field type.";s:12:"dependencies";a:1:{i:0;s:7:"content";}s:7:"package";s:3:"CCK";s:4:"core";s:3:"6.x";s:3:"php";s:3:"5.0";s:7:"version";s:7:"6.x-3.1";s:7:"project";s:9:"filefield";s:9:"datestamp";s:10:"1246665925";s:10:"dependents";a:0:{}} |

So, in that 'downgrades' folder, I removed both filefield and imagefield folders. Now it registers the correct version in the available updates folder.

Thanks for the help.

Any idea what I may have done to cause this to happen?

quicksketch’s picture

quicksketch
he/him
commented
Title: Unable to update FileField (and ImageField) » Unable to update FileField (and ImageField), Update Status says previous version still installed
Status: Active » Fixed

Drupal will find ANY module anywhere within any modules directory, regardless of if it's been nested or not. Think about how CCK includes a bunch of modules underneath the "cck" directory. Drupal scours recursively through the entire modules directory for any potential modules. The solution is simply to never keep backups where Drupal can find them, store them somewhere else, or better yet, use a version control system like SVN or Git to manage your code so you don't need to keep backups at all.

mgleahy’s picture

mgleahy commented

Ok...I actually don't recall putting those files in the downgrades folder - maybe the module uninstall feature did at some point? In any case, I think I may have forgotten to extract the filefield and imagefield modules when I first ran update.php. If so, maybe thats when it picked up those locations, and afterwards, the newly extracted files were no longer being checked.

Thanks again for the help.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.