Hi Tim,It's an old thread but I was just exploring a similar question,
and I believe this is now part of ACS Tools. See here:
Just fixed this with the great support people of Dynamic Media. The
issue was that the default invalidation template of only takes care
of the main asset, and doesn't flush the smart crops. The solution was
either to add the specific path to the required refocused smart crop in
the confirmation dialog ("The following URLs will be invalidated in the
CDN"), including the crop name, or to modify the template so that it
mentions the main asset plus all possible smart
This is an old thread! But since in 2020 I still had to google more than
usual when faced with the same question, here's the link for everyone
who'll arrive here looking for the
In AEM 6.5 we still have it, but it's officially deprecated. Meaning
frozen and no longer developed, to be removed with upcoming updates, so
best not relied upon in 2020. You can still use it however, if you
understand the limitations. In AEMaaC it is removed already.
Hi gurus, I am wondering about any new best practices around importing
custom HTML in AEM pages. The use case is evergreen: not everything
needs to become a reusable component, there are always one-off ready
designs that merely need to be served with AEM. This used to be covered
with the Design Importer component as part of the Landing Pages
functionality, but that is now deprecated in 6.5 and removed in AEMaaC.
Adobe mention an alternative in the works, but thus far, no news. The
Embed core com...