Hi,
I know that I can access the thumbnails of assets created in the dam via the following servlet:
/content/dam/images/image.jpg.thumb.100.140.png
However when I tried uploading a custom rendition following the same naming convention ie: cq5dam.thumbnail.200.100.png
I am unable to access it using the same method. Not sure what I'm missing.
Thanks,
Dmitry
Solved! Go to Solution.
Views
Replies
Total Likes
you need to write an custom servlet to handle this case
Views
Replies
Total Likes
The URL to your rendition should look like this:
/content/dam/images/image.jpg/jcr:content/renditions/cq5dam.thumbnail.100.140.png (assuming that 100 x 140 is the size you're looking for)
Views
Replies
Total Likes
you need to write an custom servlet to handle this case
Views
Replies
Total Likes
Hi Lee,
Thanks for the reply, I know that method works, but the latest antisamy library will strip anything with jcr:content in its path from text fields where I may want to use this rendition. So I was hoping to use the other way to get at it so far with no luck.
Views
Replies
Total Likes
So this was an interesting exercise in reverse engineering. I believe I have figured out - the naming conventions are 100 clear, but the key is following accurate naming conventions. If you want to access rendition with using the thumb selection (which maps to the com.day.cq.wcm.core.impl.servlets.ThumbnailServlet) you must:
Any deviation from those naming conventions and the thumbnail servlet won't work. The full path that goes down through jcr:content works no matter what you rendition naming convention, but thumbnail servlet requires the naming conventions above. You can see that naming convention in the out of the box examples:
I don't know if the flipping of the order is intentional or a bug, but it is consistent.
Views
Replies
Total Likes
Views
Likes
Replies