If a feature includes a new Imagecache preset, the preset is imported correctly. However, it doesn't actually function until I manually visit the Imagecache preset and click the 'override defaults' button, just after which I see the message 'The directory sites/example.com/files/imagecache/listing_thumbnail has been created. Once that has happened the preset works correctly.

I'm not too sure if this is a features or an imagecache problem.

Comments

Mac Clemmens’s picture

Mac Clemmens commented

I'm having the same issue. It resets every time I update the feature. I have to back through and override each preset.

mrfelton’s picture

mrfelton commented

Looks like #823888: Imagecache presents and Aspect Switcher is related.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

This is related too: #928264: Change Aspect Switcher to use presetname instead of presetid

dtarc’s picture

dtarc commented

I just came across this today. We are not using Aspect Switcher.

If I install the feature via the modules page, the imagecache presets need to be overridden before they are functional. If I install the feature via the features page, the imagecache presets are functional immediately.

While we are not using Aspect Switcher, we are using Feeds to pull in the images via a standalone import.

So the quick fix for us is to enable the feature via the features page as opposed to the modules page.

dtarc’s picture

dtarc commented

After a bit more poking around, I see that the directory path for the filefield does not exist.

So if a filefield has a directory path set (ie a subdir in the files directory), and that directory does not exist on the server where the feature is enabled, then:

  • The imagecache presets work immediately when the feature is enabled via the features page
  • The imagecache presets need to be overridden before they will function when the feature is enabled via the modules page

I added a hook_enable() that creates the directory path when the feature is enabled. Now my imagecache presets work whether the feature is enabled via the modules page or the features page.

Should features be doing this automatically when filefields with directory path set are included with the feature?

hefox’s picture

hefox commented
Status: Active » Postponed (maintainer needs more info)

This seems like an imagecache issue; it's what is supplying the default hook and such functionality. Can someone test this on latest features/imagecache + see if imagecache has an issue on this?

mpotter’s picture

mpotter commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.