Storing file in CCK field does not honor filefield path setting

I am having the same problem.

When I re-save the node, the file is then moved to the correct place.

I'd rather not have to re-save the node everytime, however.

i get the same problem

Can you check out the latest development version? I've done some modifications to how the file path is handled which I hope should resolve this.

I just tested newest cvs version (2009-Sep-17 after #263908 commit ) on fresh* drupal install. its still not possible to save to filefiled with special path defined. i get error

* for all today`s tests im using one single fresh install
BTW after not storing the thumbnail, it did placed properly the flv file in filefiled (its been not placing it before, see -> #486206: Files transcoded but not added to filefiled

So it looks the issue is:

Note the file path is wrong- Drupal can't create that directory. In watchdog, is this error coming from ffmpeg, or mm_cck?

its from filesystem

Attachment	Size
e.png	145.69 KB
file system.png	145.79 KB
log.png	224.69 KB

Can you provide the log entry for the ffmpeg entry? I'm wondering if that is the source of the error.

sorry, my mistake: sites/default/files was not writable so i did chmod a+w ~/tescik2/sites/default/

than i re-submit the filefiled setting form with the custom path and sill getting error but from "MM Content"

it get a bit messy all ready, maybe i shout test it some other way?

Attachment	Size
zrzut_ekranu.png	137.95 KB
zrzut_ekranu-1.png	143.88 KB
zrzut_ekranu-2.png	189.84 KB
zrzut_ekranu-3.png	138.75 KB
zrzut_ekranu-4.png	134.36 KB

In the watchdog log, can you see if the file referenced in event 57 (http://drupal.org/files/issues/zrzut_ekranu-3.png) is on the file system?

yes, its there

also on hd is no directory defined here (look: screenshot)

Attachment	Size
destatation.png	112.64 KB

Seems like the issue might be related to #564064: specified path has no effect

and #275293: Uploading to files/subfolder leads to files/ instead files/subfolder

with dev version of filefiled the issue is still present despite #275293: Uploading to files/subfolder leads to files/ instead files/subfolder

Attachment	Size
dev-also-problem.png	294.03 KB
couldnot.png	281.35 KB

SORRY, mistake: the #275293: Uploading to files/subfolder leads to files/ instead files/subfolder is for 5-x version

but any way dev version of filefiled is also not producing proper dir in /files. i will test the 3.0 version then according to #564064: specified path has no effect

Using filefield-3-0 things work correctly for me. Can you try upgrading and see if that works for you?

I think I just post a related topic here: http://drupal.org/node/604374

I get duplicate files, one stored in the path configured in filefield path settings and the other one in the root folder for files in drupal setup.

Using Filefield 3.x, things work almost correctly here. When I use tokens in the file path settings (eg. to automatically create a YY/MM/DD file directory structure), new directories aren't being created (eg. the 'DD' directory of the YY/MM/DD token path).

So: things work fine when the file path's directory exists. When a directory doesn't exist and should be created on a token basis as configured in file path settings, the upload fails.

(Note: I chmodded /sites/default/files to 777 in my tests to be sure it wasn't a directory permissions problem).

Did some more testing: it seems that the upload fails (see #19) because token is creating files instead of directories (I'm assuming it's token that's doing this).

For example, when the file field is configured with a file path like [site-date-yy]/[site-date-mm]/[site-date-dd], token creates a file called '19' (today is the 19th) in /sites/default/files/09/10, instead of a directory with that name (the '09' & '10' directories already existed).

This leads to an incorrect $filepath in mm_cck_field_filefield() (mm_cck.module, line 514), so the upload fails.

(When I test the same field using the node form, the filefield behaves normally: token creates a directory, and the file is being saved.)

Any idea why this is happening with mm_cc?

can you give me the input file name and the output file name? I just want to make sure i have a better idea of what's going on

Since the upload fails (*), I don't have an output file name. Or am I mis-understanding your question?

(*) By 'upload', I mean the copy action from /files/media_mover/ffmpeg/converted// to my specified (token-created) directory path in the filefield's config.

It might have to do with ownership of the subfolder.
Do a long listing (ls -l) to see who's set as the owner

If you create the subfolder then obviously you become the owner.

In my experience fileupload will only honor the path if apache is the owner.
If you set the fileupload path and let Drupal create the subfolder on the fly (on first upload) then it'll work.

futrick,

I have set the owner to apache for files/images, and chmod 777.

I have a CCK field, which has File type, and Image as widget. Path is set to images under system files/ directory.

System files/ directory was set to 777 for testing.

When I upload a picture in the add form, the picture ended up in the files directory.

So, I do not think it's a owner / permission problem.

@futrick: I had checked directory ownership & permissions before, they're correct (owned by Apache, with 777 permissions for testing purposes).

I just committed a change to mm_cck_field_widget_files_directory() which should now create the directory path when it doesn't exist. Can you give the development version a go and see if it is working?

With the current dev version, I'm getting the following error (in watchdog, coming from mm_cck):

Shouldn't the destination be the directory set in the filefield's path settings?

Did some more testing.

The error above (#27) occurs when I set the filefield's path to use multiple subdirectories in /sites/files/default, something like:

When I change the filefield's path settings textfield so it contains only one directory, files are saved correctly after being transcoded by Media mover. It works using "a static path" (as in: not using tokens), as well as using token to create the path. In this case, the path is created and the file is saved to the correct location.

When I use mutliple subdirectories, the destination seems to be set incorrectly in mm_cck (and mm_cck throws the error, see #27).

When the path consisting of mutliple subdirectories exists before transcoding the file, things also work as expected.