Hi,
before using filefield path I used the normal path settings that come with filefield. the I started using filefield path and forgot about the old paths I set up. But it seems that the "normal" filefield paths are STILL being used for the temporary upload of the files before they are being moved to their final location on node submisson. That drove me nuts as I changed my file structure and the temp paths kept creating the old file structure and I couldn't figure out where it was coming from. I fixed it by disabling filefield path, changing the paths in the normal filefield setting and enabling ffp again, now it all works. shouldn't there be a configuration option for the tmp paths or a hint that the old path are being used. other option would be to just use the root folder of the default file dir?

Comments

alison’s picture

Wow, this exact thing is happening to me, and I thought I was losing my mind! I briefly used web-fm for some stuff, and even though I uninstalled web-fm and removed it from my server, the bug you've described is happening to me to this day!!

I agree, we have to be able to change/fix the temp dir without going through all the steps you've described.

That said, I'm relieved/tentatively-excited to try what you've explained so that at least I can get everything working properly again... Thank you for sharing your fix, even though it shouldn't be necessary.

Whoever thinks they can fix this, please let me know if I can help in any way. Thank you!

Deciphered’s picture

Issue tags: +FileField Paths 2.x

FileField Paths 2.x (currently in internal development) is reverting back to the original method of using the CCK widgets fields to store the data instead of using the FileField Paths database table, which will fix this issue and a few others at the same time.

Should hopefully be a alpha/beta/dev release within the week.

Cheers,
Deciphered.

kbk’s picture

After using FileField Path for over a year, a recent upgrade has exposed me to this issue. As D6 2.x still has no stable branch, any chance of addressing this in the 1.x branch?

Deciphered’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

No longer supporting Drupal 6 issues for this module.