Though Localised XF say for header and footer, work fine with sling dynamic include on author and publisher, it doesn’t work properly on dispatcher. However with few small changes we can make this work for Localised XF’s as well. Lets see how.
Continue readingCategory: Experience Fragment
A very common use case is to use multilingual/localised XF’s for header and footer for multilingual site. By default this is how the OOTB template is available in the AEM archetype as well and is the recommended approach to implement header and footer in Touch UI.
Continue readingA very common use case is to use Experience Fragments/XF’s for Header and footer in editable template. In fact this is how the OOTB AEM archetype implements header and footer. However you would very soon notice issues with the caching of XF’s and would need to device a caching strategy. Lets discuss the issues and how to resolve them.
Continue readingA common issue with Experience fragment(XF) is cache invalidation of pages referencing the XF. When a Experience fragment(XF) is modified and published, pages which reference the XF are not updated and still shows old XF content. This happens because the XF content/html is cached as part of each page instead of being referenced from a shared location.
Page needs to be explicitly activated/invalidated to view the updated content of the XF. This can be quite tedious and unpractical at times for the authors. There are multiple ways to tackle this problem.