I've installed the module, given myself permissions, checked that my
I made a new ImageCache action and chose only one step - IM raw
I dumped in the code you had at the bottom of (your ?) example page (http://perlucida.com/blog/features/css-sprites-using-imagecache-and-imag...) for the module - namely:
-resize x400 -resize '400x<' -thumbnail 50% -gravity center -extent 200x200 \( +clone -modulate 110,0 -fill '#FF0022' -tint 100 -ordered-dither h2x4a \) +append
I've also tried other commands such as "-contrast" and "-sepia-tone" and others to try and get SOMETHING to happen, but no matter what I do the example drupal icon never changes.
At admin/settings/imageapi/config/imageapi_imagemagick I see my imagemagick info is:
Version information:
Version: ImageMagick 6.2.4 09/16/06 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2005 ImageMagick Studio LLC
I see no error messages anywhere during this process...
Can you perhaps give me some pointers or steer me in a direction where I could figure out what the issue is here?
Thanks,
Hermes
Comments
Comment #1
adrinux commentedSorry you're having problems. The example drupal icon should show the changes if it's working, clearly it isn't.
Do you have imageAPI set to show debug info? I you visit the imageAPI Configure page at: admin/settings/imageapi/config you'll see a checkbox for "Display debugging information". That at least should start showing error messages.
(But in my experience you may have to go to a page using the imagecache preset you're defining and refresh the page/visit a different page before the error appears, there's some sort of delay on the error appearing.)
I'm not sure what impact Imagemagick version would have, certainly simple commands should work, but FWIW I have this working on servers with ImageMagick 6.3.7 (debian lenny) and 6.5.1 (ubuntu jaunty).
It's obviously hard to figure out what's happening without errors.
Comment #2
hermes_costell commentedI've figured it out!
At: admin/settings/imageapi/list
I had the "Select a default image processing toolkit:" set to "ImageAPI GD2" vs. "ImageAPI ImageMagick"
I wasn't aware that not only was it the "default" image processor... but that indeed that set it to be the ONLY image processor, apparently!
A suggestion for the module: a check to see which image processor is selected by the user, and a warning message output perhaps, if this module is installed, but the image processor is not set to ImageMagick?
Also now that the mechanism is working - and thanks to your suggestion above I've enabled debugging information - I can now see an issue which is preventing this from working. To keep things clean I'll post it as a new bug.
Thanks for your help!
Comment #3
adrinux commentedThat check for whether imagemagick imageAPI is enabled sounds like a good idea :)
Comment #4
adrinux commentedA more accurate title.
Comment #5
adrinux commentedAdded a check against imageapi_gd, if its set as the imageapi toolkit an error is displayed with a link to the imageapi toolkit config page and hint to sue the imagemagick toolkit.