Image crop in html5smartimage xtype | Community
Skip to main content
rubenf42159101
rubenf42159101
New Participant
November 29, 2016
Solved

Image crop in html5smartimage xtype

  • November 29, 2016
  • 3 replies
  • 2798 views

Hi,

I'm using AEM 6.1 and I'm using OOTB Text and Image component to upload & crop images. When I crop the image, I get imageCrop properties populated with x,y,width,height values. This crop values differs with my local and DEV environment. I used the same image with same cropping in my local and in my DEV environment. 

With little more debugging, I found the value differs only when I crop images of width and height which exceeds 1000px (say 1920x1200). I read the documentation for html5smartimage and it says "the value depends on the serverside implementation"

What does the serverside implementation refers to? And why do I see a difference in values being stored in my local and DEV (with same image and same cropping applied)?

 

https://docs.adobe.com/docs/en/aem/6-1/ref/widgets-api/index.html?class=CQ.html5.form.SmartImage

cropParameter : String

Name of the form field used for posting the cropping rect; use null or a zero-length String if the cropping tool should be disabled; the value depends on the serverside implementation; use "./imageCrop" for CQ foundation's image component; "./image/imageCrop" for the textimage component

Regards,

Ruben

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by AndySh4

I don't know precisely what the issue is but here are a couple things to check. Make sure your local and dev instances both have the same service packs & cumulative fix packs. In general it's not uncommon to see subtle variations like this when your AEM instances aren't all the same. Also, sometimes the cache of AEM javascript clientlibs under /var/clientlibs/libs becomes obsolete and doesn't reflect the javascript that is installed under /libs. To be safe, back up /var/clientlibs/libs and then delete /var/clientlibs/libs and then check if the cropping behaves as expected. As you reload your cropping test page, AEM should rebuild it's cache of javascript clientlibs at /var/clientlibs/libs. 

3 replies

S
SrikantK
New Participant
May 9, 2017

The largest image rendered in AEM is according to the configurations in "Day CQ DAM Buffered Image Cache" service. As the image cross the size of 1024px(default), the image is resized. But your local has some different value(I guess). Please refer below URLs, it might help.

 

https://helpx.adobe.com/experience-manager/kb/remove-web-rendition-dimension-limit.html

https://helpx.adobe.com/experience-manager/kb/cqbufferedimagecache-consumes-heap-during-asset-uploads.html

Regards

Srikant

https://helpx.adobe.com/experience-manager/kb/remove-web-rendition-dimension-limit.html

https://helpx.adobe.com/experience-manager/kb/cqbufferedimagecache-consumes-heap-during-asset-uploads.html

kautuk_sahni
kautuk_sahni
Employee
January 30, 2017

Hi,

I'm using AEM 6.1 and I'm using OOTB Text and Image component to upload & crop images. When I crop the image, I get imageCrop properties populated with x,y,width,height values. This crop values differs with my local and DEV environment. I used the same image with same cropping in my local and in my DEV environment. 

With little more debugging, I found the value differs only when I crop images of width and height which exceeds 1000px (say 1920x1200). I read the documentation for html5smartimage and it says "the value depends on the serverside implementation"

What does the serverside implementation refers to? And why do I see a difference in values being stored in my local and DEV (with same image and same cropping applied)?

 

https://docs.adobe.com/docs/en/aem/6-1/ref/widgets-api/index.html?class=CQ.html5.form.SmartImage

cropParameter : String

Name of the form field used for posting the cropping rect; use null or a zero-length String if the cropping tool should be disabled; the value depends on the serverside implementation; use "./imageCrop" for CQ foundation's image component; "./image/imageCrop" for the textimage component

Regards,

Ruben

Kautuk Sahni
A
AndySh4Accepted solution
New Participant
December 2, 2016

I don't know precisely what the issue is but here are a couple things to check. Make sure your local and dev instances both have the same service packs & cumulative fix packs. In general it's not uncommon to see subtle variations like this when your AEM instances aren't all the same. Also, sometimes the cache of AEM javascript clientlibs under /var/clientlibs/libs becomes obsolete and doesn't reflect the javascript that is installed under /libs. To be safe, back up /var/clientlibs/libs and then delete /var/clientlibs/libs and then check if the cropping behaves as expected. As you reload your cropping test page, AEM should rebuild it's cache of javascript clientlibs at /var/clientlibs/libs. 

    Terms & ConditionsAccessibility statement

    Loading footer...