Dear @bhavya1724 , I suspect that's configuration issue - something is missing/miss-configured. You need to double check your configurations. Check in OSGI, check on your code every little detail for your database settings. These are the two things to look at. Then try to install the bundle/package ...

Hi @doodls , Hard Coded ExampleThe first example uses sightly to reference an experience fragment, /content/experience-fragments/we-retail/equipment, and the required variation, master. This will only work when the path includes the experience fragment variation path. The value here is hard coded. <...

Hi @ibmfur , Kindly refer this article: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/onboarding/demo-add-on/screens.html?lang=en Hope it helps you! Regards, Santosh

Hi @NitroHazeDev ,According to SLING-4805[0], ResourceResolver should properly extend AutoCloseable[1] as of Sling API 2.11.0. So if you are using Sling API 2.11.0 you should be able to refactor all of our try-catch-finally resource resolver code to try-with-resources[2] and my suspect is your below...

Hi @jeremyc82321732 , AEM HTL Read–Eval–Print Loop - helps to achieve that. "A live code editing environment for HTL templates with optional server-side JavaScript logic, executed on an Adobe Experience Manager instance. This little tool is great for learning HTL and for experimenting with it, becau...

Hi @gopi38 , Can you check on "/system/console/jcrresolver" and enter "/sites.html" into the field below "configuration test"? It should result in something like this: Hope that helps! Regards, Santosh

Hi @Vani1012,   Core component version 2.20.8 is not compatible with AEM 6.5.11, Please refer this link below https://experienceleague.adobe.com/docs/experience-manager-core-components/using/versions.html?lang=en Hope that helps! Regards, Santosh

Hi @Vani1012, Page Decomposition You can check those component references by appending ?debug=layout querystring at the end of url. eg. http://localhost:4502/editor.html/content/mysite/us/en.html?debug=layout It gives all the references of component which has been used on the page as below. For mor...

@TB3dock You can create the package as I mentioned above instead manual writing and import it in your file system. 

Hi @TB3dock , The traditional way of having groovy script should have .content file since it's jcr:primaryType nt:file. Next, you can create the Importer class. This will be responsible for reading and running a script.  import groovy.lang.Binding; import groovy.lang.GroovyShell; import lombok.AllAr...