Is there a fix for this in the dev version? or anywhere? Thanks.

Comments

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

Please describe the actual issue in detail and I might be able to give you a real answer.
Module versions, steps to reproduce, configuration options, and any other relevant information would be greatly appreciated.

Cheers,
Deciphered.

ddbell’s picture

ddbell commented

The filefield paths is not storing the images in the proper location for image caches that use the "Add Scale" setting only.

specified in the file path: [user-name]/[field_story_date-date]. It works for image caches that use the crop setting. It also works for upload and image modules.

Modules:
imagecache 6.x-2.0-beta10
cck 6.x-2.5
image_fupload 6.x-3.0-rc2
filefield 6.x-3.2
imagefield 6.x-3.2
imagefield tokens 6.x-1.0
imageapi 6.x-1.6
file alias 6.x-1.x-dev
filefield paths 6.x-1.3
tokens 6.x-1.12

Steps to Repeat:
Create imagecache and select "Add Scale" setting only
Create sample content type and create field using image fupload [file type = file, widget= image fupload]
Configure the field for image fupload: set the file path = [user-name]

It should place the uploaded files in the files/[user-name] directory

If you change the imagecache to "Add Crop", you will see it works fine.

Thanks.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Priority: Critical » Normal
Status: Active » Closed (fixed)

The file does get stored in the requested directory, but based on the way that Imagecache works, it creates another version of the file with the requested actions at the path: /files/imagecache/[preset]/[user-name]/file.ext

This is expected behavior and has nothing to do with FileField Paths.

Sorry for the terribly slow response time, haven't had much time to dedicate to FFP of late.

Cheers,
Deciphered.