Hi,

today I evaluated FileField Paths and ran into some strange behaviour. I've configured File name and File path settings on two fields, each re-used in several content types. The settings of all fields are identically and are made of Global tokens (site-date-xxx). I've created the content types including the file fields before I've installed the FileField Paths module.

This works fine for the first content type I've set up and tested the configuration. On all other content types, the FileField Paths settings seems to be ignored, i.e. all files I've uploaded are stored directly in the "files" folder and are not moved to the configured subfolder. Unfortunatly there are no error messages, indicating a problem. (I'm not sure if it has ever worked on any but the first content type, as I've copy-and-pasted the settings to all other content types without testing each immediately or if it stopped working after some time).

After trying a lot of things, I changed the path settings, saved the content type, changed it back to it's original value and saved it again. Now it works. I have done this change-and-change-back for all my fields in all content types and now everything seems to work fine.

Even this workaround is working for me, I think this is not an intended behaviour. Is this a known problem? What could be wrong?

Thanks for your help (and this great module),
Nils

Comments

socki’s picture

socki commented

I've notice something similar to this.

On a site that i'm working on, i noticed that the issue is that the settings for the given field do not appear to be in the 'filefield_paths' table.

In my case, this happened because I had exported the content type declaration as part of a feature, then installed/enabled it on a different site. When going to the the settings page for one of the fields in question, it appears that everything is set up properly. The problem is that if you were to look in the 'filefield_paths' table, there is no data for that field. If you edit the field and save, this table then gets populated and the directory paths work as intended.

xjm’s picture

xjm
she/her
Primary language English
commented

I discovered this today as well... I am now reconfiguring paths for every single filefield. The table was completely empty. Worrisome, as I use paths with .htaccess to protect certain files. At least with the retroactive update feature I should be able to get the files back to where they belong.

I haven't been able to reproduce the problem after reconfiguring, though.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Issue tags: +FileField Paths 2.x

While I can't confirm this issue, the changes that are currently being made to the 2.x version will fix this as the data is stored with the FileField instead of in a FileField Paths table.
Expect a alpha/beta/dev release within the week (hopefully).

Cheers,
Deciphered.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Status: Active » Closed (won't fix)

No longer supporting Drupal 6 issues for this module.