Thanks. I am trying to understand why it behaves the way it does. And a programmatic fix rather than having to ask Template Authors to go through the work of putting content in, just to remove the component they just added to the template.

Perhaps I have to elaborate on the issue. Here is how to reproduce:1. Lets say we have two components - Component A and Component B.2. Component A has simple HTL, say<h1>This is Component A</h1>3. Component B has following HTL<h1>This is Component B</h1><div data-sly-resource="${'content' @ resource...

We have a component with a coded in responsive grid (code below). When we add this component to the editable template, template author could not delete any more. Search on forums turned up something that vaguely referenced Synthetic Resource and need to create content using cq:template.Appreciate if...

Figured it out. The solution was quite obvious (and silly). Agents (specially the ones used for flushing activity) on publish need  "On Receive" checked on the Trigger tab of the agent configuration. And it also needs "Ignore Default" checked.  Looking back, it makes complete sense.

We are using AEM 6.4 .  Are there changes in replication agent component / api that results in this behavior only on Publish ? Thanks.

Thanks. I did review the other thread. That issue was result of space in the agent name (and on Author instance).In our case, I can confirm that there are no spaces in the agent name (akamai).Following scenario with works . on Author instance:1. New agent created with name "akamai"2. Content publish...

We have need to flush akamai cache on replication and built a custom agent following an (older) project on Github. GitHub - nateyolles/aem-akamai-replication-agent: How to create custom replication agents in AEM using Akamai as an exam… Then we created agent under "Agents on author". UI shows up, we...

AEM Cluster documentation mentions that only slave nodes does not delete the clustered.txt when shutdown normally.However, my observation with AEM/CQ 5.5 (and 5.6) is that master node will not delete the clustered.txt even if its shutdown normally (stop script)IF other slave nodes in that cluster ar...