As a rule of thumb it would help understanding cache variations if you imagine each unique variation of the page URL as a separate output cache item.
Each variation is stored in output cache as a separate item with unique key, however all variations of the page use a single page compilation.
To solve the above described problems, Sitefinity CMS enables you to fine-tune the page output cache invalidation behavior.
When you edit a page or one of its dependencies, which would traditionally result in invalidating the output cache, you can instruct Sitefinity CMS to serve the current cache version of the page to website visitors for a predefined short period of time, and meanwhile warm-up the new version of the page in cache in the background.
However, problems can easily arise when a tenant makes a mistake that could invalidate your landlord insurance.
If you’re hiring builders, check they have suitable insurance and let your insurer know.
In order to prevent the above issues from occurring, you as a landlord have a set of responsibilities.
These apply before a tenancy begins and during the period that tenants are living in the property.
Hi, We are currently experiencing a problem with users not logging off Portal, but just closing their browser (x) and when they go back into Portal, it does not prompt for their userid/password, but takes them directly into Portal.