Page 2 of 3

Custom Namespace in AEM

Why a namespace is required?

Assets metadata in AEM might be updated from multiple 3rd party systems. Namespaces help us identify the source of the metadata.

To persist custom metadata properties to the binary. Unless a namespace is attached to a property, the property will not be persisted to the binary.

Continue reading

Caching issue with Experience fragments

A 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.

Continue reading
« Older posts Newer posts »