Hello! I'm running Drupal 6.18 and I've recently upgraded from FileField 6.x-3.7 to FileField 6.x-3.10 but after updating the module I still get the notification as if it's not updated (as you can see in the screenshot I'm attaching)... I guess there should be some "traces" in the DB of the previous version (as I can see in the system table) but before deleting/changing anything manually there I rather report it :)

ps: I have even tried removing the folder completely from my modules and adding it again and I've run update.php several times as well...

CommentFileSizeAuthor
filefield_update_issue.png37.39 KBvaleria_gc

Comments

quicksketch’s picture

quicksketch
he/him
commented
Category: bug » support

Yes that happens from time to time. Try the following:

- Clear your caches at admin/settings/performance.
- Run cron.php.

FileField does not have any control over version numbers beyond what is specified in the filefield.info file.

Another thing to check based on this screenshot: I noticed that Drupal thinks that FileField is installed under "modules/cck/filefield", in which there are a couple of things wrong. Usually "filefield" is not under "cck" and usually you put modules in "sites/all/modules" not just "modules". The most likely situation is that you have two copies of FileField floating around and Drupal is finding an older copy of the module.

valeria_gc’s picture

valeria_gc commented
Status: Active » Fixed

Thank you for your reply; I guess that was a bit late yesterday and I didn't even notice the module was really under CCK. Updating that module there fixed the update alert!
I know custom modules should be under sites/all/modules but, actually, this is a project I didn't start myself and some things weren't done the way they should (like placing the modules in the right place or like filefield being inside of cck/modules...).
Thanks again!

Status: Fixed » Closed (fixed)

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