In general AEM development we will try to include all components client libs into one client lib (using client libs embed property).With this approach we are loading all the css/js where components on a particular page may not be using all that css/js as we might have dragged and dropped few compone...

We are migrating from Signal to Launch. We had set up rules and migrated all script libraries. We have added Launch code snippet to the head tag of our page.In the console we are getting below error._satellite.__registerScript is not a function.We have tried loading required script libraries to page...

Tried the move option and able to rename if I select the node which I am trying to move. Thank you for the reply.But this is indirect way and not user friendly specially for authors. Authors are expecting direct way they had it with classic UI (siteadmin) way.

Thank you Gaurav for responding.Move will allow us to rename the page,but move will actually move my page from place to other place (from one node to another node). I do not want to move the page, I am looking for copy and paste the same page and rename that page.

Hi team,In siteadmin classic UI  (http://localhost:4502/siteadmin)interface when ever we copy and paste a page we have option to rename the pasted page.But when I copy paste a page in sites touch UI (http://localhost:4502/sites) we are not getting option to rename a pasted page. For renaming we have...

In AEM 6.4 we are noticing certain folders under /libs are grayed out. We have not seen thing AEM 6.1.Are they deprecated or are we not supposed to extend/use/refer them?Any one please let us know the exact reason Why certain folders are grayed out in AEM 6.4 under /libs

Understood. Thank you for the response. Do we have any Adobe documentation where we have them in OSGI service container in 6.1 and we have to wrap those Java LIBs into an OSGi bundle and deploy to AEM in 6.4 instance. Currently I am trying to solve these issues in my local 6.4 instance.Can you pleas...

Same code working fine with out any errors when deployed to AEM 6.1. Getting errors only in 6.4.  Do I have to get all the jars for those which I am getting Cannot be resolved but is not required  errors, add those jar files to one and convert that to OSGI bundle and deploy that to OSGI console?

I am trying to migrate my code base from AEM 6.1 to 6.4. When I do >mvn clean compile -Pauto-deploy. Build is success and able to see bundles in AEM System console.  But couple of bundles are in Installed state. I am seeing lot of "Cannot be resolved but is not required" errors.But the same code is ...

Is the WebP supported in AEM 6.1/6.3. If it is not supported is there a custom way we can make out AEM to support  WebP.