In your upgrade notes for 6.x-3.0-rc1 you state the following:

Important upgrade note: The "FileField Token" module has been merged back into FileField so that it is no longer a separate module. When upgrading, delete the filefield_token directory entirely. All the functionality of filefield_token is now included in filefield.token.inc.; but the ony place where I can see filefield.token.inc. is inside filefield_token!!!

So if I download 6.x-3.0-rc1 untar it, and see the new contents of it , there is a directory called filefield_token; should I delete this directory?, if so why is it there in the first place ?

Should I delete the filefield_token in sites/all/modules/filefield/filefield_token ?; makes no sense since in order to update filefield module I have to delete the entire sites/all/modules/filefield directory

Should I delete it after upgrading and after doing update.php ?

Please clarify which, where and when When upgrading, delete the filefield_token directory entirely

Comments

quicksketch’s picture

The filefield.token.inc file is in the root of the the FileField install.

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/filefield/?...

The correct upgrade process is:
- Delete the old module directory
- Upload the new modules directory
- Run update.php

quicksketch’s picture

Category: bug » support
Priority: Critical » Normal
Status: Active » Closed (duplicate)

I think the instructions are quite clear. See #421220: Cannot redeclare filefield_token_list().

So if I download 6.x-3.0-rc1 untar it, and see the new contents of it , there is a directory called filefield_token

There is not. You probably untarred the new copy over the old one, which doesn't delete old files, it merges the two.

vr_mex’s picture

For some reason when downloading from the Available updates page in my Drupal admin page,
the 6.x-3.0-rc1 was downloading a version that did not have in the root directory the filefield.token.inc file and did have the
filefield_token dir on it!!!

I tried again and all is fixed seems there might have been a problem with caches holding an old version, weird....

thanks a lot