This is a product bug and fixed in SP 10.Please install Service Pack 10 and validate the same. The reference number for the product bug is CQ-4329416.  

Just take the request param i.e. the page path and use the same in the query described in the comment above. It will resolve your business requirement. There is no direct API to find the assets & content fragment used on the page & which are still valid. Thanks

 ACS AEM Commons Report Builder - This is used just for reporting. It is not possible to do automatic processing with the result of the report. If only reporting is to be considered, then only one should go with the " ACS AEM Commons Report Builder".

Hi, Just create a query in your servlet to get the list of the assets/contentFragment. Query for testing it on http://localhost:4502/libs/cq/search/content/querydebug.htmltype=dam:Assetpath=<page-path> Finally create the same using  Session session = resourceResolver.adaptTo(Session.class); if(nul...

Hi, For restricting the any pre-defined property, navigate to the "/system/console/configMgr" and search for the configuration "Apache Jackrabbit Oak Solr indexing / search configuration". Within the particular configuration there is a field "ignored properties". Add the pre-defined property which y...

Hi, Here you need to choose an image preset that is responsive (designated by the RESS button after you select it). There is a step by step documentation available which describes how you can get the responsive images with dynamic media. Reference:- https://experienceleague.adobe.com/docs/experience...

In the AEM Maven archetype 22 there is a module called repository-structure. The module's description says it all:Empty package that defines the structure of the Adobe Experience Manager repository the Code packages in this project deploy into.Any roots in the Code packages of this project should ha...

Hi, I tried creating the configuration directly through crx/de and it worked fine. I am using AEM 6.5.5. Please check while you are creating the configuration, if the node is properly created or not. I tried under the path "/apps/system/config" and under the project specific run mode as well.  Thank...

In that case either you can use the jobs and process then serially, if you want it to be processed one by one.

Ideally the permission should never be applied at the lowest level, as later on if the size of the repository increase then there are lot of challenges in modifying the permission for the groups or users at the lower level nodes. I would suggest to create a group at a higher level until really neede...