I am trying to update to a newer version if filefield (6.x-3.0 to any higher version up to 6.x-3.3) but no matter what I do update.php does not recognize the newer versions.

Comments

quicksketch’s picture

It sounds like you might have 2 versions of FileField installed on your site. Drupal might be finding an older copy of FileField and using that instead of your updated version.

Anonymous’s picture

Hi Quicksketch,

How is that possible when my server shows only one instance of filefield? And what can I do to repair it if this is the case?

Also I'm not sure if this could be related but I've found in messing with this is that my theme(Aqcuia Slate 6.x-3.x-dev) prevents me from using any upload widgets. It starts the upload then stops after a few seconds with no error. It just wont upload. Basically I'm only able to upload images, files, etc if I change my theme to garland or something other than Acquia Slate.

quicksketch’s picture

When you view your Drupal site, Drupal will only load one version of FileField module. However you might have multiple copies of the module located on the file system, such as in sites/all/modules/filefield and in sites/default/module/filefield. To make things more confusing the module could be in some random place like sites/all/modules/modulex/filefield. I suggest you search through your installation and check there aren't two copies.

Or an easier approach to checking which copy is ran, look in your "system" database table and that will say where filefield is being loaded from.

Anonymous’s picture

Status: Active » Fixed

quicksketch,

A quick search of the DB "system" table found a rogue filefield module stashed in the mp3 module. Must have been a drag and drop error. Deleted this module. Installed 6.x-3.3 and (even though it wasn't necessary) ran update.php. Module is now displaying as proper version.

As a side note: the uploading problem has now been resolved. I can now upload media while viewing the site in the Acquia Theme.

Thanks,
nycjomo

setting this issue to "fixed"

Status: Fixed » Closed (fixed)

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