Experience Fragment issue in Dispatcher

Avatar

Avatar
Validate 1
Level 2
rupalig70586203
Level 2

Likes

6 likes

Total Posts

11 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
rupalig70586203
Level 2

Likes

6 likes

Total Posts

11 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
View profile
rupalig70586203
Level 2

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)

Avatar

Avatar
Give Back 5
Level 3
anujg3325839
Level 3

Likes

27 likes

Total Posts

26 posts

Correct reply

8 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile

Avatar
Give Back 5
Level 3
anujg3325839
Level 3

Likes

27 likes

Total Posts

26 posts

Correct reply

8 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile
anujg3325839
Level 3

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 (5)

Answers (5)

Avatar

Avatar
Give Back
Employee
Bruce_Lefebvre
Employee

Likes

28 likes

Total Posts

62 posts

Correct reply

28 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Give Back
Employee
Bruce_Lefebvre
Employee

Likes

28 likes

Total Posts

62 posts

Correct reply

28 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile
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.

 

Avatar

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile
Gaurav-Behl
MVP

22-01-2019

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

Avatar

Avatar
Level 1
akshatas5875550
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
akshatas5875550
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile
akshatas5875550
Level 1

30-09-2020

Is there any solution for this? I am facing the same issue for content fragment as well.

 

Thanks

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

645 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

645 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
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

Avatar

Avatar
Level 1
weil22989506
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile

Avatar
Level 1
weil22989506
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile
weil22989506
Level 1

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?