Hi @kyasam  The LDAP users are essentially aem users and migrating LDAP users to 6.5 will be same as migrating aem users. The below article will help you in migrating users, groups and acls to different env. https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16448.html?lang=e...

Hi @anasustic  The service user which you are using to get the resource resolver might not have "modify" access to the resource you are trying to modify. Please check the permissions for this service user.

Hi @Mario248  What you need is a pathBrowser. You can refer the below. <pageList jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/pathfield" fieldLabel="Logo Path" name="./logoPath" required="true" rootPath="/content/abc"/> 

Hi @akhilraj  You cannot get the sessionStorage from SlingHttpServletRequest. You will have to pass the value saved in the sessionStorage to the API. For ex while you are making the ajax call from your JS, you can fetch the value from the sessionStorage and pass it as a query param. JS snippet: var ...

Hi @robertol6836527  You can use the below curl command to clear the dispatcher cache. curl -H "CQ-Action: Delete" -H "Content-Length: 0"  -H "Content-Type: application/octet-stream"  -H "CQ-Handle: /content/my-project"  http://localhost/dispatcher/invalidate.cachecurl -H "CQ-Action: Delete" -H "Con...

Hi @jakdevmode  Your component doesn't have the scope to the variable "clientlib". Try adding the below line of code above the data-sly-use.<sly data-sly-use.clientlib="/apps/myproject/components/sightly-templates/ctagrouplegal/ctagrouplegal.html" ></sly> Thanks 

If you don't want this behavior to happen in your header then you have to make necessary changes to your header component. Thanks

I haven't tried it myself but it should be possible. You can programmatically roll out pages from JAVA backend. So it should be possible from groovy as well. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-rollout-a-page-programmatically-and-update-references-aem/m-p/40...

You can do that using groovy scripts if there is a logic to knowing which pages it has to be enabled. Like, enable this for the first 2 pages on a child page or something like this?

Hi @chinmayis865517  There is a page property called "Hide in Navigation" which is used for this purpose. You can enable this option for pages a and c. When you are constructing the sitemap you can choose to ignore the pages with "hide in navigation" enabled. RegardsJeevan