As you are using Use API, which is actually converted into JAVA instead of loading as a JS in a browser, you have to use JAVA object to log the information. Below code is working fine on my local. log.info("Using USE API"); Also this log will be generated in server log files instead of browser conso...

You can download older AEM version specific documents from Software Center and install it on your local AEM instance as per this documentation. https://experienceleague.adobe.com/docs/experience-manager-release-information/aem-release-updates/previous-updates/aem-previous-versions.html  

@goonmanian-gooner  You can use “extraClientlibs” property on the dialog to load a clientlibs applicable only for it. You can add your custom logic in this clientlibs.There are few things that you need to take care of when using extraClientlibs : 1. DO not include every custom JS client library into...

When you start the workflow using workflowSession, it starts the workflow in a different thread. So your Scheduler wont know whether it will be getting failed or not. You should refactor your workflow logic/process to avoid getting failed. There is a thread based approach to validate the status of w...

Please confirm where exactly you are getting the error. Which line of code is failing.    Please check this link : https://helpx.adobe.com/in/experience-manager/kb/Random-Resource-resolver-is-already-closed-in-the-logs-AEM.html  

You can write query on component resourceType and get count for various scenario. For example I did for list component which is configured either for Child pages or Static pages. Use case 1 : static pages path=/content/we-retail 1_property=sling:resourceType 1_property.value=weretail/components/cont...

@R_R_P  I see you are referring 2 different artifacts. Core Components artifact and Core Component Examples artifacts are different.  Below dependencies work fine. Please check. <!-- Core Components --> <dependency> <groupId>com.adobe.cq</groupId> <artifactId>core.wcm.components.core</artifactId> ...

I have faced similar use case but in my case Tags were getting removed from cq:tags property if the tags does not exist in the repository(/content/cq:tags). This was happening only with OOTB cq:tags property but not with the other custom tag based property. So it looks like your content is still tag...

@goonmanian-gooner Basically if the OOTB model of core component is not providing you the functionality as per your requirement, you can override it using delegation pattern.  Refer this link which explains the concept nicely https://levelup.gitconnected.com/aem-extend-core-component-models-using-re...

This should work in your case try { Map<String, String> map = new HashMap<>(); //update query as per requirement map.put("path", "path"); map.put("type", "dam:Asset"); QueryBuilder queryBuilder = resolver.adaptTo(QueryBuilder.class); Session session = resolv...