The model at https://github.com/adobe/aem-core-wcm-components/blob/master/bundles/core/src/main/java/com/adobe/cq/wcm/core/components/internal/models/v1/ListImpl.java does not export a method like getListItems , It has  getItems() . So you can call it like shown below data-sly-use.list="com.adobe.cq...

If you dont define cq:allowedTemplates at  /content/experience-fragments. then what AEM would do will list all the templates matching the regEx i.e. /content(/.*) . As experience-fragments is under /content, the regEx matches and the templates get displayed. The rendering logic can be found via this...

The failed sling jobs details would be printed in the error.log file with the stacktrace.You can analyze those.

Purging version would definitely reduce the repository size. However, you would need to wait for the compaction cycle to happen for that. If you are on AEM 6.3 and above, online compaction would reclaim this space at 2:00 AM server time (default configured time) To determine if version purge ran suc...

Hello @sajithv  The most probable cause is that your servlet bundle is not installed on the publisher. Please ensure the following: 1. The node you created has sling:resourceType defined. It should have the value you mentioned in the servelt2. Ensure your bundle is installed in the publisher and is ...

This package is not available publically. To work with the tutorial, you need a valid account with Analytics and target. If you have it, you can simply configure them in AEM and you don't need this package.

@mpalme1 The way your image is stored in a page is by storing its reference. So, you first go to crx/de and investigate content/we-retail/us/en/men/after-install/jcr:content/root/responsivegrid/contentfragment. Do you see the image reference? If you see the image reference, then check for the image....

 This issue is resolved with the latest version of Chrome Version 83.0.4103.97 (Official Build) (64-bit) You can also raise a support ticket to get a fix if you are not upgrading Chrome 

This issue is resolved with the latest version of Chrome Version 83.0.4103.97 (Official Build) (64-bit) You can also raise a support ticket to get a fix if you are not upgrading Chrome 

@shaileshb584084  For which version of AEM are you facing this behaviour? I tried on AEM  6.5.0 and could not reproduce. Can you please open a support ticket for this so that this can be further looked into.