This document contains information for an outdated version (3.0) and may not be maintained any more.

If some of your projects still use this version, consider upgrading as soon as possible.

3.0.10-rc1

Upgrading

  • If relying on partial caching of content between logged in users, be aware that the cache is now automatically segmented based on both the current member ID, and the versioned reading mode. If this is not an appropriate method (such as if the same content is served to logged in users within partial caching) then it is necessary to adjust the config value of SSViewer.global_key to something more or less sensitive.

Security

General

Changelog

Comments

Comment policy: Please use comments for tips and corrections about the described functionality.
Comments are moderated, we reserve the right to remove comments that are inappropriate or are no longer relevant. Use the Silverstripe Forum to ask questions.

blog comments powered by Disqus