I develop on a WAMP localhost and then move my site online to LAMP Hosting.
In the process of moving, everything related to imageAPI/imagecache works fine, except for my rounded corners.
The issue: The imagecache preset that produces rounded corners on my WAMP local host produces the correctly scaled image, but without the rounded corners.
I have attached screenshots of the presets for both the WAMP and the LAMP installations showing that the WAMP works and the LAMP does not, the imagecache modules in use, and the PHP GD setting on the LAMP installation that does not work.
I am using PHP 5.2.9-2 on the WAMP install that does work and PHP 5.2.10 on the LAMP install that does not work.
What I have tried so far:
I have flushed the presets and flushed my cache on the LAMP site, it continues to produce images incorrectly, without the rounded corners.
Moved the site from WAMP to LAMP twice to make sure there was not a problem in the move.
Reinstalled and updated all the modules.
Any guidance would be much appreciated.
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| PHP GD Info on LAMP that does not work.JPG | 45.48 KB | vanderlip | |
| Preset Does work on WAMP localhost.JPG | 63.41 KB | vanderlip | |
| Modules in Use on both installs.JPG | 104.14 KB | vanderlip | |
| Does not work on LAMP hosting.JPG | 81.32 KB | vanderlip |
Comments
Comment #1
vanderlip commentedCorrection to the above post
"The issue: The imagecache preset that produces rounded corners on my WAMP local host produces the correctly scaled image, but without the rounded corners on my LAMP host."
Comment #2
dman commentedGood problem report, but I'm not sure what could be causing this.
Your versions look up to date - newer than the ones I first developed on I think - so no problem there.
I can only imagine something odd inside GD.
I guess you are not using imageMagick by accident, if the database is a clone.
Can you confirm the later 'define canvas' works? Your output is 125x125?
As a test, I'd try swapping the define canvas underlay for a change-format to PNG. Just to see if it makes a difference. define canvas is better for your needs, I just wonder which step is not working.
Rounded corners can be a processor/memory-intensive job the way it's being done ... however that REALLY shouldn't be hurting at all with a 121x121 image. So that's unlikely.
... I wish our 'default image' had corners to look at ;-)
I see you are using a private file system. I don't know if that makes any difference - certainly shouldn't AFAIK - but worth noting.
Not sure...
Comment #3
vanderlip commentedDman -
Thanks for your quick and friendly assistance. I tried your suggestions but could not make it work, so I ask my hosting support folks. They were able to fix it, based on their response below. I am in way over my head in understanding the fix, but I am posting this in hopes in might help others. Should I post something over at the Image API module issue page or just leave it here? Obviously, I can't confirm whether or not this is the right fix, but it did work for me.
For anyone like me, who is not a developer or super technical in any way, I would add that having a hosting company with excellent support is essential. Cut rate hosting rarely gets you service like this.
At any rate, this can be closed. Thanks for a great module!
"Hello,
If you turned off antialiasing from the configuration of Imagecache, then the image would have been displayed properly.
We did some changes on your account, so that image conversion works properly all the time (even with antialiasing). The problem is related to a bug in the function imagecopyresampled(), which affects the color transparency on some versions of GD. We added the following lines:
imagealphablending($res, false);
imagesavealpha($res, true);
in the file "sites/all/modules/imageapi/imageapi_gd.module", on line 126. This seems to have fixed the problem.
You can find more information on the problem in Internet:
http://www.google.com/search?q=imagecopyresampled+png+transparent
Please, check the image conversion now. If you need any additional assistance, you can always get back to us.
Best Regards,
Support"
Comment #4
farald commentedClosing issue.
Comment #5
dman commentedI just gotta say, that is one of the best, friendliest, informative, pro-active and useful support tickets I've ever seen.
Above and beyond the call of duty, they delved into code that wasn't their responsibility and fixed it anyway!
Kudos!
I'll bounce this over to imageapi, because that's where those guys (who clearly knew what they were talking about) thought the fix was needed. Imageapi has come and gone a little with transparency support, I know, but we're still working on it.
As far as I can tell from the feedback, it may come down to something screwy in the GD version, and I was not able to replicate, so I'm still not sure what the story is.
If nothing else, it's a great example of a full problem report (yay venderlip) and a happy solution (yay vanderlips ISP) so I'll share.
(Feel free to close again - it's just an FYI for the imageAPI queue)
Comment #6
drewish commentedanyone mind rolling a patch for this?
Comment #7
drewish commented