Hi @krishna_chaita2,in case you want to avoid customizations in /apps, you can try to upload your static HTML page in /content/dam and remove the text/html mime type from DamContentDispositionFilter. Hope this helps,Daniel  

Hi @Ravi_Joshi,check if your replication-service user has jcr:readAccessControl permissions on the root path. Good luck,Daniel

Hi @NeilKe,I haven't used Redirect Manager from ACS Commons but your logic sounds OK. In case an OSGi component has the "policy = ConfigurationPolicy.REQUIRE" parameter set, then it only gets activated when you configure it on a specific environment. Good luck,Daniel

I think you definitely need to add a piece of custom JS here. As your logic is based on user interaction, this cannot be achieved on the server. I don't see how HTL templates could help here. Good luck,Daniel

Hi @sofiyans8042875,this is for sure possible. With every CDN, including the Adobe-managed Fastly, you can redirect traffic to different origin servers. See https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-configuring-traffic#origi...

Hello,In my project, we have been using classic Dispatcher stat level-based invalidation from the start. This worked fine until we didn't add a lot of content fragments, custom APIs, etc. Now we need custom Dispatcher flush logic to invalidate API paths or pages using queries to fetch the data from ...

I can confirm what @EstebanBustamante said. Interestingly, overlay doesn't work but you can still copy-paste stuff from /libs to /apps, delete what you don't need, and extract it with a package to your codebase. Good luck,Daniel

Hi @user96222 in AEM you can customize almost anything. If you overlay the client lib and remove the category that is used to load it, it will stop loading on the page.The question is why would you want to overlay an existing clientlib from Adobe? I never had that use case. You should create and loa...

Thanks for pointing that @arunpatidar, we didn't want to install the complete package so the team copied the code expecting it to contain the logic for both on-prem/cloud, but now I see there is a different version for Cloud.

Hello,is anyone using ACS Commons - Dispatcher Flush Rules on AEMaaCS? It is working fine for me locally with the SDK, but when I deploy it to Cloud DEV I get the following error: com.day.cq.replication.AgentNotFoundException: Replication triggered, but no agent found! The error happens on the call ...