Experience Fragment issue in Dispatcher

Avatar

Avatar

rupalig70586203

Avatar

rupalig70586203

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!

View Entire Topic

Avatar

Avatar

Bruce_Lefebvre

Employee

Avatar

Bruce_Lefebvre

Employee

Bruce_Lefebvre
Employee

30-09-2020

Hello,

 

The exact behaviour of the dispatcher in this situation will depend on your configuration:

  1. Is the dispatcher configured to use TTLs (via the `/enableTTL` setting)?
  2. Or, is it using .stat file based invalidation with a dispatcher flush agent?

In case #1 above, the time-to-live on the content in question (often set with the ACS AEM Commons Dispatcher TTL feature) will need to expire before the page will be "refetched" from the publish tier.

 

In case #2, .stat files will be "touched" in the cache (to update their last modified timestamp) when the dispatcher flush request is received. The exact stat file(s) which are touched will depend on the `/statfileslevel` configuration. A value of "1" in this case should work, but may cause additional unnecessary load on the publish tier by re-rendering pages which are otherwise unrelated to the published XF. 

 

Another approach to case #2 would be to leverage the ACS AEM Commons Dispatcher Flush Rules feature to create "smarter" flushing schemes, which could flush your HTML content at specific paths when an XF is published.