Hi @sankar07 ,I can see there are multiple 302 redirects happening which is not needed. Try below rules and modify as per your need. 1st to make sure the redirection is to https and 2nd one to append /content/brand. More [R] redirects are not needed in my opinion. You can have PT flag instead:-RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^/?$ https://brand.com%{REQUEST_URI} [L,R]RewriteCond %{HTTP_HOST} ^brand.com$ [NC]RewriteCond %{REQUEST_URI} ^/$RewriteRule ^/$ https://brand.com/e...

Hi @jakdevmode ,The object of clientlib you are creating could be the issue-Please refer the below code sample - For each component, you will have to create the clientlib object as it is created in 1st line. If you just include in top of your page (only in page component), the other components will not inherit the object. If you are writing the data-sly-call attribute in you component html, you have to re-create the clientlib object in the same way it is created in above sample code.

Hi @james-mke ,You are seeing the right documentation. There is no OOTB way to detect the duplicate images when you upload through the asset API. The configured OOTB functionality works when you upload it via browser UI or through AEM desktop. For Asset API, in this documentation http://experience-aem.blogspot.com/2021/03/aem-cloud-service-assets-server-side-check-for-duplicate-file-names.html you will have to write the filter which is this point 3) Add a filter apps.experienceaem.assets.core.fi...

hi @akhilr48142671 ,Check some of the examples of similar case here - https://www.tabnine.com/code/java/methods/com.day.cq.dam.api.Asset/getLastModified

Hi @Keerthi97 ,There are couple of things I can suggest here:-If for your requirement you can manage just to have a unique id for every time a component is dropped in a page- ex- testcontainer-someUniqueId, then use this documentation. You can have a js code to manipulate the component just by searching the id. - https://aem.redquark.org/2019/12/generate-id-for-aem-components.htmlif you have to use 1,2,3... then you will have to right a custom js snippet which will iterate through the dom by kee...

Hi @juancarlos2022 ,Looking at the image, it seems like you have some customization in your base page properties which is making it disable. This could have been done intentionally within your project. This is not how AEM OOTB page properties looks like. I would recommend to verify each property on the basepage within your project to check where what is causing this. And for reference, create a fresh AEM instance and go to page properties for we-retail and verify. Also, if in dev stage and prod ...

Hi @sai_rama_krishn ,You can utilize CUG concept in order to achieve this. see this example - https://experienceleague.adobe.com/docs/experience-manager-learn/assets/advanced/closed-user-groups....Just this configuration will not help you to achieve this, you will have to write a custom authentication handler. As soon as the user tries to access the restricted asset, you can show a form popup or redirect and have a form where you will collect the user data, once the data is collected you will re...

Hi @SahrudayaB ,Here the client is your AEM instance and server is the webpack where you are accessing the same AEM content without the authoring capabilities.In the documentation you will see "proxy": "http://localhost:4502",which means we are proxying this AEM instance and rendering all the content on the webpack server for the view. It will be like end user view without any authoring capabilities. And any change you make in the AEM authoring page, you will see that reflecting adhoc on the web...