Hi @Asutosh_Jena_    Can you please let me know what is the use case here? In general, the publisher should be restricted from being accessed as an admin.   Thanks,Kiran Vedantam

Hi @Ricky99999    You can achieve your use case in the below ways: use query builder API to get the properties you wantuse page or node API and getting the value map of the resource and finally write them into an excel file in java   Query builder sample query: path=/content/we-retailtype=cq:Pagepat...

Hi @sathishtb1    You can do it at the template level   Hope it helps! Thanks,Kiran Vedantam

Hi @P_V_Nair    Check if this article helps you: https://blog.developer.adobe.com/optimizing-aem-search-queries-9049d272df3b   Hope it helps! Thanks,Kiran Vedantam

Hi @Vani1012    What exception are you seeing in the bundles? Is it related to core components only or is it related to any other bundles?     Thanks,Kiran Vedantam

Hi @Lakshmi9    You can add a path browser option in the dialog to author the videos from DAM. In your HTL, add the below code for the HTML 5 video player   <video data-sly-attribute="${model.attributeMap}" id="my-video" class="video-js" controls preload="auto" poster="${properties.fileReference}" d...

Hi @Kam-nyc    Can you please be more specific on what you are trying to achieve? The CORS behavior, commonly termed CORS error, is a mechanism to restrict users from accessing shared resources. This is not an error but a security measure to secure users or the website you are accessing from a poten...

Hi @Tessa_learner1    The default style should help you with this. Can you please check if the other styles that you are adding are having any alignment changes as well? Also, please note that your changes would be overridden on the build if you don't have them in your code.   Hope it helps! Thanks,...

You dont need to close the resourceResolver coming from workflow session, check if anything else is causing the issue.

Hi @NitroHazeDev    If you would obtain a resourceResolver You did not open the resolver from a request or workflow session and do not need to close it.   Check if there is any other resource resolvers causing it.   Thanks, Kiran Vedantam