Retroactive like behavior when changing token source

Put me in for this functionality! :)

this would be horrible to do automatically. Then you could really mess up tons of pages on your site with a simple change..

Please if this is implemented make it ONLY optional, and surrounded by as much red tape as possible.

The last thing I want is an administrator making an 'improvement' and making all files previously uploaded to the site no longer show up.

Hope this is the right issue to add my thoughts to...

I have been testing how filefield_paths 6.x-1.3 works with image node creation as a token-compliant alternative to #103793: Add token support for image file directory and image names. It seems to work fine when creating image nodes; the uploaded file and derivative images are moved to the path created from the node's relevant token values (in my case tokens relating to taxonomy).

However when I edit an image node, change some taxonomy, select the "Rebuild derivative images" option on the image node edit form, then save the node without uploading a new image file, the "original" image file is left in the previous path but the derivatives are re-created in the default image path. I think this is because although filefield_paths_filefield_paths_process_file() is called during a node update, the image file is not identified as "new" so no action is taken by this function.

I would not expect ever to create paths from node titles, but taxonomy is a powerful feature and I do sometimes upload an image and set the taxonomy wrongly first time.

If I can think of some more specific suggestions I'll add them to this issue.

+1 and subscribe. This would be grand.

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