Forums / Developer / ImageMagick command and watermark
laurent le cadet
Tuesday 15 June 2010 5:49:50 am
Hi,
I'm trying to apply aa image as watermark on an image alias like this :
[ImageMagick]Filters[]=watermark=-composite -gravity center extension/ezwebin/design/ezwebin/images/watermark.png
[lightbox] Reference= Filters[] Filters[]=geometry/scaleheight=600Filters[]=watermark=
But the generated image is only image design for the watermark. No composite of watermark.png and images.
Any hint ?
Laurent
Robin Muilwijk
Tuesday 15 June 2010 5:55:36 am
Hi Laurent,
Have you seen the following topic http://share.ez.no/forums/developer/imagemagick-watermark-filter-not-working. They were able to solve the watermark problem there.
Regards Robin
Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation. LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk
Tuesday 15 June 2010 6:18:44 am
Thanks Robin,
I'm turning around this topic for hours now without any correct result. I tried almost everything -composite -watermark +swap ...I can only see my watermark image or ...nothing.
:(
Reinhard Hutter
Tuesday 15 June 2010 9:23:48 am
I had the same problem recently, many of my image filters stopped working. By trial and error I found out that I have to put the filename in front of -composite, e.g.
Filters[]=banner_watermark=design/plain_site/images/banner_mask.png -composite
I still don't know if eZ has changed or the ImageMagick syntax had changed.
Tuesday 15 June 2010 11:46:01 pm
Thanks Reinhard,
It's also the solution for me (4.3.0).I tried to apply more parameters e.g.
Filters[]=banner_watermark=design/plain_site/images/banner_mask.png -composite -gravity center
but in that case, only the "background" image is show.
Anyway, it's a big step forward ;)
STEVO +
Wednesday 16 June 2010 4:10:01 am
This is due to this enhancement in 4.3.0:
http://issues.ez.no/IssueView.php?Id=16022&activeItem=1
I've posted a comment but I think it should be opened as a bug.
You can patch it by reverting lib/ezimage/classes/ezimageshellhandler.php to the 4.2.0 version.