Hi,
I'm experiencing some problems when importing imagecache presets via features. They all seem to be there when viewing the imagecache presets page - but aren't loaded into the actions/presets imagecache tables (perhaps that's normal?). Then they don't actually have the proper effect on images.
I'm using:
Features 1.0
Imagecache 2.x-dev latest tarball
Pressflow core (based on 6.19)
PHP 5.3
Along with these imagecache action modules:
smartcrop
imagecrop (javascript_crop action)
Also, the javascript_crop action works fine on the imported feature - but doesn't save properly because in the 'imagecrop' table it saves the record with a presetid of 0 - presumably because it can't identify the presetid of the imagecache preset its editing.
I'm not quite sure where the issue lies - with the action modules, with the imagecache import/export, or with how features handles the import/export - and I'd appreciate any guidance for troubleshooting please.
My hunch is that smartcrop and imagecrop simply don't support having imagecache presets and actions in code and are directly going to the DB to look for information rather than using the imagecache API. But is it right that imagecache doesn't populate the imagecache_actions and imagecache_preset tables with the data import from the Feature?
Thanks very much
Steve
Comments
Comment #1
steveparks commentedWith further testing, everything works fine as soon as I override the imagecache presets imported via the Feature - which of course brings them into the database.
This suggests that the problem is that actions modules are looking direct to the imagecache DB tables rather than using the imagecache API. How could they access these presets and actions in a better way that would be Features compatible?
Otherwise, should imagecache import the presets into the database anyway?
Thanks
Steve
Comment #2
steveparks commentedUpdate:
I have opened tickets in other modules....
#933934: Smartcrop doesn't support Imagecache presets in Features
#923908: Imagecrop doesn't support Imagecache presets in Features
In the first ticket greg.harvey suggests a solution for modules that rely on imagecache to call an imagecache function to get a normalised list of all presets regardless of whether they are in the DB or code.
Comment #3
kobnim commentedI am having a similar problem with the imagecache_actions module (http://drupal.org/node/999346). The preset does not appear in the imagecache_actions table, and I am looking for a work-around.
When you say:
Could you please tell me ... how do you "override the imagecache presets imported via the feature"? If I go to admin/build/imagecache, there is no "edit" link next to my imported preset.
Comment #4
dublin drupaller commented@ kobnim "Could you please tell me ... how do you "override the imagecache presets imported via the feature"? If I go to admin/build/imagecache, there is no "edit" link next to my imported preset."
there should be an OVERRIDE option to the right of your preset. clicking on that will allow you to edit it.
I'm having the same problem as others....when I install the image presets feature on another drupal installation, it doesn't appear to work as expected.
Am looking into it. Will post back up here if I find out a workaround/solution.
Comment #5
fizk commentedPlease reopen if this is still an issue with ImageCache 6.x-2.0-rc1.
Comment #6
ryan.ryan commentedThis is still happening, just migrated some content types and the imagecache preset won't be created.
Comment #7
ryan.ryan commented