Experience Fragment issue in Dispatcher

rupalig70586203

21-09-2018

Hi,

When we are publishing experience fragment only, its not updating the page in which we are using that XF in dispatcher.

Below are the steps we have followed:

  • Create and edit an XF and publish it.
  • Create a page and add XF created in previous step and publish the page.
  • Now edit the XF and publish it. Do not publish page.

In publisher, we are able to see the the XF content updated in page even if it is not published. But in dispatcher we are seeing old content only.

Please suggest if we need any configuration change for this.

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

anujg3325839

21-09-2018

dispatcher flush listeners get triggered when a replication/publish request get initiated. In your case no activation, hence no dispatcher flush. You need to publish the page after XF change to get cache updated or write your own listeners.

Answers (3)

Answers (3)

Gaurav-Behl

MVP

22-01-2019

One of the solution that works is ACS Commons Dispatcher Flush Rules

Briankasingli

MVP

17-12-2019

Hello @rupalig70586203,

AEM does not provide out of the box solutions to flush (re-activate) pages that have a reference to the experience fragment. You need to create your own solution.

One technique can be, on a non-heavy load website, After re-publishing an experience fragment, you can contact your cloud engineering team to flush the entire cache of your website. But keep in mind, the CPU consumption of your publishers will be affected negatively, especially if you have heavy user activity at the given time.

Another technique, as a quick solution for clearing experience fragment cache, is to have the authors use the touch UI, "manage publication", to republish all pages. However, this action will also publish site pages that are currently being edited.  

Check out this website for more caching experience fragment techniques and ideas: https://sourcedcode.com/caching-experience-fragments-with-aem-sites-6-5

weil22989506

22-01-2019

We ran into a similar issue, where the fragment is used in multiple pages, obviously it's a big pain having to re-publishing all of the pages whenever the fragment is changed. Is there a config that would invalidate all of the pages whenever the fragment's updated?