Cache manager

To enable caching for the system, select on in this field. Once you have turned caching on, Matrix will start caching your system. By default, this field is enabled.

The method used to store and retrieve cache objects.

This field allows you to set the number of cache bucket directories to use for caching. The cached information is stored as files in these buckets (or directories). The maximum number of cache buckets created for storage is this number squared. If you set a low number, each bucket retains many cache files. You may start to reach the limit on the number of files in a directory imposed by your server’s operating system. If you set the value too high, each bucket will hold a small number of cache files, which can be inefficient in terms of performance.

Set the length of time (in seconds) the cache file is valid. By default, this field is set to 86400 seconds (24 hours). For example, if you want the cache to be refreshed every three hours, you would enter a value of 10800. When an asset is updated, the cache is not automatically cleared until the default expiry time has elapsed. As a result, some changes may not appear on the frontend of your site until the next time the cache is refreshed.

Set the length of time (in seconds) that the requested page is cached within a proxy accelerator, such as Squid cache. This field is set to 86400 seconds (24 hours).

Set the length of time (in seconds) that the requested page is cached in the browser. This field is set to 1800 seconds (30 minutes).

When enabled, Matrix will automatically clear the Matrix cache on assets whenever their attributes or metadata are updated.

When enabled, Matrix clears the Proxy cache automatically on asset URLs whenever the asset attributes or metadata are updated.

If enabled, when a public user requests a page within your site, Matrix will first look in the cache for the public page. If it does not exist in the cache, it will build the page from scratch. Signed-in users never see the public cache version.

This setting is only applicable to signed-in users. If enabled, when a signed-in user requests a page within your site, Matrix will first look in the cache for the appropriate asset according to that user’s highest available permission setting (read, write, or admin). This means the cache will be shared amongst users who have the same permission setting on the asset. If it does not exist in the cache, it will then build the page from scratch.

This setting is only applicable to signed-in users. If enabled, when a signed-in user requests a page within your site, Matrix will first look in the cache for the version of the page for the user groups to which they belong. This means the cache of the asset will be shared among users who belong to the same parent user groups. If it does not exist in the cache, it will then build the page from scratch. You should only use this option if you are using user groups for permissions instead of roles or individually assigned permissions. These settings will only work if the Caching status is On.

This field allows you to select for which asset to clear the cache. With the additional fields on this screen, you can clear the cache for this asset only, this asset and its children, or this asset and its dependents. You can also specify for which asset types that you want to clear the cache. For example, you can clear the cache for all of the news items under your site.

Select whether you want to clear the cache for the asset(s) only, the asset(s) and its dependents, or the asset(s) and its children. The asset(s) that will be used are specified in the chosen asset field above. The dependants of an asset are those that cannot exist without that asset. For example, the page contents asset of a standard page or the question assets belonging to a custom form. The children of an asset are those that have been created underneath it in the hierarchy.

Select for which asset type to clear the cache. For example, if you want to clear the cache for all news items in your site, you would select your site in the choose asset field, this asset and its children in the level field, and news item in the asset types field. You can select multiple asset types from the list. If you want to clear the cache for all asset types, select – all asset types – from the list.

If set to yes, Matrix will also send a clear Squid cache request for the URLs applied to the assets specified above that get their Matrix cache cleared.

The home page asset is selected.

This asset and its dependants are selected as we only want to clear the cache for the home page and the bodycopy assets under it.

As we only want to clear the cache for the home page, Standard page is selected from the list. Once the screen is saved, the cache for the home page is cleared.

The site asset is selected in this field.

This asset and its children are selected as we want all news items under this site to have their cache cleared.

As we only want to clear the cache for the news, news item is selected from the list. Save the screen, and the cache for all news items will be cleared and not for any other types.

This field shows the current setting for cacheable headers however the setting can not be changed. This option is configured on the System configuration screen.
For more information on the send cacheable header field, read the System configuration screen documentation.

You can specify the protocol to send cacheable headers on, either HTTP only, HTTPS only, or both. By default, this field will be set to both.

The cache control levels of each protocol can be individually set in these fields to either public or private.
By default, both these fields will be set to public. For more information, refer to w3’s cache control documentation.

This is a unique header setting for use with squiz edge and caching content for authenticated users. Contact Squiz for more information on this feature, as it only applies to systems that use the trinity caching module with their Squiz Edge caching configuration.