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.hi
Sorry if this is a wrong place, but I think my problem is related to your module.
I have token and filefield modules enabled.
When I'm creating new field (File) I can use [uid] token in file path: profile_video/[uid] in my case.
So.... I'm trying to upload new file - it says: creating profile_video folder, creating profile_video folder/[uid] folder
BUT... file uploaded into files/ folder instead of files/profile_video/id
If I'm trying to create another node (same type) under the same user - it works correctly and uploading file in right place.
So... problem seems exists when folder (specified in field settings) not exists.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | filefield_path_check5.patch | 2.37 KB | quicksketch |
| #6 | patch-more-than-2-nonexisting-dir.txt | 2.37 KB | abhaga |
| #2 | sub_folder.patch | 2.58 KB | drupalprojects |
| #1 | sub_folder.patch | 2 KB | drupalprojects |
Comments
Comment #1
drupalprojects CreditAttribution: drupalprojects commentedok. I've changed issue title cuz this is not related to token. I don't have much time right now to explain what was causing this bug, but I've prepared a patch. Test it and let me know what you think. Thanks
Comment #2
drupalprojects CreditAttribution: drupalprojects commentedOpps, forgot to add checking for token_replace in above patch.
Updating....
Comment #3
jpetso CreditAttribution: jpetso commentedFrom a quick look, this looks like it might be correct. Please give me a bit of time still until I'm done with the Drupal 6 port, then I'll get to your patch. Thanks for your help!
Comment #4
dopry CreditAttribution: dopry commentedThe error message seems incorrect... The file was successfully uploaded, but the destination directory could not be created, so the file could not be saved...
Comment #5
quicksketchI confirmed this is still a problem in the 2.4 release. I'd like to revise this patch so that it doesn't need to have several nested "x ? y : z" conditionals.
Comment #6
abhaga CreditAttribution: abhaga commentedHi,
I have also run in to the same issue both with ImageField and Filefield. As per my understanding the problem in the in the filefield_file_insert and imagefield_file_insert functions. Basically the filepath for uploading the file is created before nonexistent directories in the path are created with a call to filefield_check_directory. As a result, directories are created but the files still go to files directory.
The problem can be reproduced by trying to upload a file into a path with at least last 2 directories on the path nonexistent.
A patch against 5.x-2.4 is attached which corrects this issue. Imagefield patch is similar and I will post it there. Have been using this for few months now and seems fine.
Regards,
Abhaya
Comment #7
abhaga CreditAttribution: abhaga commentedComment #8
quicksketchThanks abhaga, committed. Just some code style fixes in the attached patch.
Comment #10
tanma CreditAttribution: tanma commentedHi there
In searching, this seems the best thread for this problem.
Using file field 6.x-3.9,
The problem I'm experiencing is similar in that when the file path (in my case photoalbum/[user]) doesn't exist, the images are saved in files/ folder.
My problem is different in that the file path photoalbum/[user] folder is never created. Whether the first, second or third node. Only if I manually create the folder will the images be saved in the correct folder.
Does anyone have any ideas on why this is happening? I've checked the folder permissions of the files/ folder. I haven't worked out how to implement a patch but not even sure this one (#8) would help in my case. Any help would be appreciated (seems a simple problem but can't seem to fix it).
Tan