@PrakashBa2 Could you check the latest version? Posted above code for your understanding.  

@PriyaNair1  Can you confirm whether read permissions are granted to the Anonymous user on the publisher instance? A 403 or 404 error can occur if the requested resource is not accessible to unauthenticated users. This often happens in the publish environment, where the Anonymous user (which represe...

Hi @sunny_gvp, IMO, the issue could be because of:  Authentication Token / Session Not Available AIO CLI relies on a locally cached access token or interactive login, which may not persist or be accessible in headless environments like cron. Solution: Use Service Account JWT or OAuth integration (v...

Hi @PriyaNair1, I think, the issue may not be with the dispatcher alone. Here are several potential root causes and how to resolve them: 1. ClientLibs not replicated to publish Even if filters are in place, the actual content (clientlibs) must exist on the publish instance. Check: On the publish in...

Hi @aravindS, I don't think so! Not all questions in the Adobe AD4-E117 practice test (https://certification.adobe.com/courses/1030) necessarily have guaranteed correct answers. The practice test on the Adobe certification site is meant to simulate the exam environment and help candidates understand...

Hi @AbilashRa, I think, you cannot dynamically set values like the page title in the initial/.content.xml because that XML is static and processed at template creation time, before the page is created - so dynamic values like jcr:title from page properties aren’t available yet. May be you could try ...

Hi @PrakashBa2, Try below options whichever you think is best suitable according to your case   Option 1: Switch to RESOURCE_RESOLVER_MOCK Instead of JCR_MOCK, use: public final AemContext context = new AemContext(ResourceResolverType.RESOURCERESOLVER_MOCK); This is faster, more isolated, and doesn'...

Hi @PrakashBa2, Your test cases are failing due to incompatible or outdated test dependencies after moving to AEM 6.5 LTS. Try below steps steps to fix it Update test dependencies in your pom.xml: <dependency> <groupId>org.apache.sling</groupId> <artifactId>org.apache.sling.testing.sling-mock....

Hi @tushaar_srivastava, Let's understand your query by breaking it down: SELECT * FROM [nt:base]: This fetches all node types extending from nt:base, which includes all nodes in the JCR repository. WHERE [jcr:uuid] = $id: This filters nodes by their universally unique identifier (jcr:uuid). $id is...

Hi @NavyaVo, You can give this a try -  adding a few practical ways to manage this as below: 1. Use AEM page permissions to restrict replication AEM controls the visibility of the "Publish" buttons based on replicate permissions. Steps: Navigate to /content in Useradmin or CRXDE Lite. Deny the rep...