I've uploaded latest imageField and fileField, but they don't update. What's the process?

You need to run update.php after uploading the new files. Other than that there isn't anything special you need to do other than upload the new files.

When you say, "I'm still being told I need to update" do you mean that update status is simply telling you to update? You might manually run cron (just visit the cron.php file), which will make update status refresh the versions of modules it thinks you have installed.

I've been having the same problem and in fact just posted an issue before seeing this. Since alpha7, each updated seems to have been ignored. I've tried to update with rc1 and final 3.0 numerous time, however the module still shows up as 3.0-alpha7 in admin/build/modules as well as admin/reports/updates (the update page where it asks me to upgrade to 3.0.

Checking the .info file shows that the module is in fact version 3.0. I've erased the module, fresh download re-install, updated.php, cron, nothing. It still says I'm running version 3.0-alpha7.

I can confirm this issue. During an update from 5.x to 6.12, using Filefield and Imagefield 3.0 (full release), I see the following message in the "Select versions" list when I run update.php:

filefield module can not be updated. Its schema version is 2. Updates up to and including 3 have been removed in this release. In order to update filefield module, you will first need to upgrade to the last version in which these updates were available.

Imagefield has a 6003 update listed, but it won't run until filefield's update runs - it throws up an error to that effect after I click Update.

Both modules are listed as up to date in the "Available updates" page, and both show up as 3.0 in the modules list.

*edit* I did a comparison with imagefield.install and saw that the function filefield_update_last_removed() returns 3, while the imagefield function returns 2. I then changed filefield's return to 2 and the updates run normally.

incrn8, the problem you're describing sounds different than other users. Per the UPGRADE.txt file, you should always upgrade your D5 site to the latest version of the module for Drupal 5 prior to upgrading to Drupal 6. In the case of FileField, updates 1, 2, and 3 (the Drupal 5 updates) cannot be run in Drupal 6 because the API functions used in content.module no longer exist. The module MUST be upgrade to the latest Drupal 5 release, then upgraded to Drupal 6.

Patch against 3.0's filefield.install attached.

The Drupal 5 version of FileField: http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/filefield/f...

The last removed update for FileField was definitely filefield_update_3(). As I said incrn8, I think you're describing a separate issue (and I don't think it's a bug at all, just incorrectly upgraded).

Ah, OK, I see. So probably the 5.x site wasn't upgraded to 5.x-2.3 then. Hence the problem. Thanks for clearing that up.

For those using D6.x along with the Calendar module, I seem to have solved the problem for my installation. One of our IT team members noticed that there was a second installation of FileField inside of the calendar module (i.e. sites/all/modules/calendar/filefield/...). Removing that entire /calendar/filefield/ directory cured my problem. Now I see that I am in fact running FileField 3.0!

I have no idea how that secondary installation got there though our site was originally built by an outside party.

Hope this helps some of you out there.

Seems that everyone's issue has been resolved here.