Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have a multiple imagefield with already uploaded images. I have tried the dev version for changing their filenames using tokens. The filenames changed smoothly, but the files didn't end where they should.
In the imagefield I have an imagepath rule: [user]/images
I have added a filename rule: [author-name-raw]-[fid].[filefield_paths-ext]
And I have pressed the retroactive changes option.
The files have been renamed, but they have ended in the files directory, not in the files/user/images directory.
It seems retroactive changes only take into account filename changes, but ignore paths.
Comments
Comment #1
Deciphered CreditAttribution: Deciphered commentedFarreres,
Thanks for the info, will test your scenario and see if I can reproduce the issue.
Cheers,
Deciphered.
Comment #2
Deciphered CreditAttribution: Deciphered commentedConfirmed as an Issue, only occurs with ImageFields in Drupal 5.
Working on a fix.
Comment #3
Deciphered CreditAttribution: Deciphered commentedLooks like this issue affects FileField Paths full stop, not just the retroactive changes functionality. Possibly related to a recent change in Imagefield?
Comment #4
Farreres CreditAttribution: Farreres commentedNo idea. People working on imagefield should be contacted perhaps?
Comment #5
Deciphered CreditAttribution: Deciphered commentedNa, she's right mate, turns out it may have been broken for a while now.
Figured out the source of the problem, just have to write the fix.
Comment #6
Farreres CreditAttribution: Farreres commentedAny news about the fix?
Comment #7
Deciphered CreditAttribution: Deciphered commented@Farreres
I'm flat out with other projects at the moment, but I assure you that I will do my best to get a fix committed in the next few days.
Comment #8
Deciphered CreditAttribution: Deciphered commentedFixed and committed to DRUPAL-5.
You will need to re-set the path settings for the field as the issue was that it wasn't being stored.
Unfortunately the damage that has already been done will have to be fixed manually as the database entry for the files location is different to the true file location.