This document contains information for an outdated version and may not be maintained any more. If some of your projects still use this version, consider upgrading as soon as possible.


Session support in PHP consists of a way to preserve certain data across subsequent accesses such as logged in user information and security tokens.

In order to support things like testing, the session is associated with a particular Controller. In normal usage, this is loaded from and saved to the regular PHP session, but for things like static-page-generation and unit-testing, you can create multiple Controllers, each with their own session.


Session::set('MyValue', 6);

Saves the value of to session data. You can also save arrays or serialized objects in session (but note there may be size restrictions as to how much you can save).

// saves an array
Session::set('MyArrayOfValues', array('1','2','3'));

// saves an object (you'll have to unserialize it back)
$object = new Object();
Session::set('MyObject', serialize($object));


Once you have saved a value to the Session you can access it by using the get function. Like the set function you can use this anywhere in your PHP files.

echo Session::get('MyValue'); 
// returns 6

$data = Session::get('MyArrayOfValues'); 
// $data = array(1,2,3)

$object = unserialize(Session::get('MyObject', $object)); 
// $object = Object()


You can also get all the values in the session at once. This is useful for debugging.

// returns an array of all the session values.


Once you have accessed a value from the Session it doesn't automatically wipe the value from the Session, you have to specifically remove it.


Or you can clear every single value in the session at once. Note SilverStripe stores some of its own session data including form and page comment information. None of this is vital but clear_all will clear everything.


In certain circumstances, you may want to use a different session_name cookie when using the https protocol for security purposes. To do this, you may set the cookie_secure parameter to true on your config.yml

  cookie_secure: true

This uses the session_name SECSESSID for https connections instead of the default PHPSESSID. Doing so adds an extra layer of security to your session cookie since you no longer share http and https sessions.

API Documentation

Was this article helpful?