Cropping Image Renditions Instead of Scaling | Community
Skip to main content
JonMaguire
Level 3
September 15, 2017
Solved

Cropping Image Renditions Instead of Scaling

  • September 15, 2017
  • 2 replies
  • 2971 views

Is there an OOTB way in AEM 6.2 to crop image renditions on upload similar to how Wordpress handles renditions?  Currently the workflow is just resizing the image.

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 manoj_devapath

I dont think OOTB provides croping image renditions by default similar to wordpress.

we have similar issue when migrating from wordpress to aem. The ACS AEM Commons Named Transform Image Servlet allows specific image transforms to be defined centrally via OSGi configurations. It has ability to Crop the image to the specified bounds.

Named Transform Image Servlet

Only issue I faced using this your use case/ component cropping bounds has be analyised before hard coding(this can be changed at any time in fly since this is OSGI configs) and acs-commons version(we were using much lower version by then).

If this also not solve your use case then you have to go for custom logic to handle new cropped image rendition

2 replies

kautuk_sahni
Community Manager
Community Manager
November 3, 2017

Moving this thread to AEM Assets!!

Kautuk Sahni
manoj_devapath
manoj_devapathAccepted solution
Level 5
November 3, 2017

I dont think OOTB provides croping image renditions by default similar to wordpress.

we have similar issue when migrating from wordpress to aem. The ACS AEM Commons Named Transform Image Servlet allows specific image transforms to be defined centrally via OSGi configurations. It has ability to Crop the image to the specified bounds.

Named Transform Image Servlet

Only issue I faced using this your use case/ component cropping bounds has be analyised before hard coding(this can be changed at any time in fly since this is OSGI configs) and acs-commons version(we were using much lower version by then).

If this also not solve your use case then you have to go for custom logic to handle new cropped image rendition