Closed (fixed)
Project:
ImageCache
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
8 Feb 2008 at 05:03 UTC
Updated:
16 Feb 2008 at 00:11 UTC
I'm having a problem with the cropping of GIF files (and only GIF files). I am using ImageCache to make 2 thumbnails for user picture uploads, and my presets both first scale the image then crop it. However, with GIF files only, the cropping step doesn't seem to run - only the scale step. With JPGs, both scale/crop work fine, and I end up with square thumbnails every time, regardless of what the original dimensions are. Any ideas?
Comments
Comment #1
tj2653 commentedTo update this issue, the problem with the cropping of GIF files only happens to me when I'm using the ImageMagick Toolkit. When I switch to the Built-in GD2 toolkit, it works properly.
The GIF thumbnail should turn out to be 125x125 (using ImageCache Profiles, which first scales and then crops), but it comes out with the width larger than the height, and with transparent borders on the left and right side. I'm running ImageMagick 6.0.7. I've duplicated the issue here: http://drupal.org/node/219929 with some additional details and sample pics.
Comment #2
tj2653 commentedI have the same issue using a different Drupal installation that has ImageMagick 6.2.8.
Comment #3
drewish commentedyou might try the imagemagick toolkit in a recent version of the image module and see if that helps.
Comment #4
tj2653 commentedHi drewish,
I'm using a patched version (with the viewport crop fix) of image.imagemagick.inc v 1.3.2.14, which is the same as what is in the latest version bundled with image-5.x-1.x-dev (2/13/08).
Thanks
Comment #5
drewish commentedalso might want to see about upgrading imagemagick. they're up to 6.3.* now...
Comment #6
tj2653 commentedYes, I updated to the latest ImageMagick 6.3.8 02/12/08 release last night, and it still didn't help :( I'm wondering if it's just my installation, or if other people have the same issue, but haven't tested that particular case yet. I might end up building a new Drupal installation and test each piece one by one to see if I can identify where the problem is coming from.
Comment #7
tj2653 commentedUPDATE: I believe it's working now. Not exactly sure what did it, as I did a few things, but two things I definitely needed were the patch in http://drupal.org/node/183688 and a current version of IM. Thanks!
Comment #8
tj2653 commented