Config changes invalidating cache

Rated 3.85/5 based on 518 customer reviews

Ideally, dispatcher cache invalidation is as specific as possible, so items in the cache live their longest possible life, however creating general stat level rules to achieve this can be tricky.

For example, if a website section , leaving the rest of the web site’s content safely cached.

Whenever a page, or its template are modified, the page's compilation is invalidated and should be precompiled.

This is the slowest part of the page rendering process.

By default, when a cached version of a page is created, this version is tied to a number of dependency objects - like the content items displayed on the page, or the page template.

Editing any of the dependencies causes the cached version of the page to be invalidated.

(It is likely this has been previously configured if you are already using Publish-side flushing).

By default, a Sitefinity CMS page has a - the one you use to access its content.

If you have a widget on the page, that displays a list of content items, each of these items has a URL, which is formed using the page base URL and the URL formatting rules for the content module.

Delete the entire cache when a new package is activated.

On AEM 6.2 or above, this service uses a Service User for repository access.

Leave a Reply