@christopherv662 this might be related to permission. Can you check if appropriate permissions are in-place?

Hi @varaprasadande1, placing packages in install folder works fine. You can use this approach.

You can populate this value in the HTML and later grab this value in JS while rendering the page.

We are using dispatcher rewrite rules for convert a url into selector based url.for example, end user is accessing the url https://www.abc.com/sample/, dispatcher is redirecting it to /content/abc/xyz/test.sample.htmlNow, the cache has been created under root with path /content/abc/xyz/test.sample.h...

ACS commons dispatcher flush is not compatible with AEMaaCS, hence can't use this.

Yes, even we tried the same using replication API. but it is not working. Cache in the dispatcher is not getting cleared or as mentioned in the thread above, that file will be deleted when we execute the code. It is not happeningsnippet looks something like this. ReplicationOptions options = new Rep...

Since it is a AEMaaCS, we can't do that as well.is there any other option for this?

@aanchal-sikka Yes, that is an option but it is not aligned with the use case.we have to clear the cache with selector in the URL. URLs can be as follows./content/abc/xyz/test.sample1.html/content/abc/xyz/test.sample2.html/content/abc/xyz/test.sample3.html Now, all of these page cache need to be cle...

We have tried this.Since the resource,/content/abc/xyz/test.sample.html doesn't exist, we get the warning com.adobe.cq.cloudconfig.core.impl.ConfigurationReplicationEventHandler Resource [/content/abc/xyz/test.sample.html] not found for ReplicationAction. Page cache has not been cleared and we are s...

We have a scenario where we have some dynamic page. These pages have been handled by AEM dispatcher( and getting cached in AEM dispatcher. These pages do not exist in AEM instance.As a next step, we have to clear the cache for these pages using replication API. The page URL contains a selector in th...