This is because of the function _image_filename(), which is a straight copy from image module ;)
So this creates a new filename for the image, saving it in files/images, which is image module's default path.
The setting for the field is not being used.

This code will get the right path:

  $type_name = 'TYPE NAME';
  $field_name = 'field_FIELD NAME';
  $type = content_types($type_name);
  print_r($type['fields']['field_composer_image']['widget']['image_path']);

Comments

vordude’s picture

vordude commented

You're absolutely right.

It all was taken straight from the original image_import.module to begin with. That bug (it's hard to even joke that it's a feature) is left behind.

would love to see a patch :-) it's on my todo list..

vordude’s picture

vordude commented
Status: Active » Postponed (maintainer needs more info)
messenger’s picture

messenger commented

any progress on this? I've got my cck imagefield upload path set to use the folder image/[user-raw].
When I allow users to import images into the imagefield from the ftp server import folder, their images are being place in the image folder, not the image/[user-raw], which I would much rather have them in.

wulff’s picture

wulff commented
Status: Postponed (maintainer needs more info) » Fixed

This has been fixed in version 5.x-1.5. The module now uses the path from the imagefield, and support tokens if the token module is enabled.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.