Please, can some one help me with this?
I have the same exact question - what good are the renditions if the users can't access them?
Exactly! I haven't got any good answer to my question, still waiting
Can any one help? Thanks
Rendions are different representations of the same asset. In CQ, components should know best, which rendition to use for their particular purpose. This is why they are not directly accessible to the end use in Content Finder. They are accessible, however for advanced users in DAM Admin in the renditions tab.
I completely agree with you and I am aware of all the programmetic ways of dealing with renditions. But I still feel that, when marketing(or business) teams are given the capability to drag and drop the assets on a CQ page from content finder, why not they can be allowed to perform the same capability with renditions? I still don't understand the logic behind such an implementation.
Also, users have been questioning the purpose of renditions, if they are not able to use them(by drag and drop) from content finder. Since they want this ability, they are feeling that all the images need to be manually converted to various sizes and uploaded to DAM rather than they are automatically rendered by DAM workflow.
Appreciate your help!!
I completely agree with you Murali. Curious as to why the standard
components would not support the multiple renditions - is it because some
customers don't opt for the full DAM?
In fact, the images are rendered by the image component, so users should never have to resize manually and upload a rendition. For web authors, renditions simply should not matter.
That sounds right to me. To clarify, are you saying that the image component will decide the right rendition according to the situation on the page rather than user to decide on it?
I don't think it works that way - if a large file image is loaded into the
DAM, that is what gets loaded on the the page not the smaller versions.
The image can be resized for display, but the file size remains the same.
I just checked this behavior. In CQ 5.5, an image dropped in an image component OEM is trunct'ed to fit the column or parsys that it is added to. The image remains 100% full-scale and flush left. In the past as a CQ architect, I have participated in the conversation no less than 10 times. If fact I discussed this with a client last week. They insisted on being able to use renditions as part of content.
I've advised on various solutions. The most complex solution I've advised on will autosize the image component to fit the column it is used in without author intervention. This is, however, predicated on the column components to be rewritten using a grid system and not %. It's extremely complex and changes the behavior of various components dramatically.
I agree I don't fully understand or embrace the philosophy on this one. I see the purist attitude toward renditions of images but its not practical in the field. Under the current philosophy images of the same size and scale will be cached in multiple locations.
Lars, feel free to school us on this one... it's your baby.
TJ, you are right - the image component cannot magically figure out the available witdth of the surrounding paragraph system, and thus it will always use the constraints set in design mode. What you should do is drop a component into the page, then open design mode and set maximum width for the image component. The image itself will be served by the image component - and the path will be something like http://localhost:4502/content/geometrixx-outdoors/en/_jcr_content/par/image_fc5b.img.jpg/1 335129761092.jpg and not contain /content/dam - when you open this image directly, you will see that is resized exactly to the desired format on the server-side.