The purpose of the registry is to store key-value pairs of information. It can be considered an equivalent to the Windows registry (only not as complicated).
You might use the registry to hold information that your script needs to store across sessions or requests.
An example would be a setting that needs to be altered by a PHP script, which currently is not possible with TypoScript.
Another example: The Scheduler system extension stores when it ran the last time. The Reports system extension then checks that value, in case it determines that the Scheduler hasn’t run for a while, it issues a warning. While this might not be of much use to someone who has set up an actual cron job for the Scheduler, but it is useful for users who need to run the Scheduler tasks manually due to a lack of access to a cron job.
The registry is not intended to store things that are supposed to go into a session or a cache, use the appropriate API for them instead.
The registry table (sys_registry)¶
Here’s a description of the fields that can be found in the
|uid||int||Primary key, needed for replication and also useful as an index.|
Represents an entry’s namespace. In general, the namespace is an
extension key starting with
The purpose of namespaces is that entries with the same key can exist within different namespaces.
|entry_key||varchar (255)||The entry’s key. Together with the namespace, the key is unique for the whole table. The key can be any string to identify the entry. It’s recommended to use dots as dividers if necessary. In this way, the naming is similar to the syntax already known in TypoScript.|
|entry_value||blob||The entry’s actual value. The value is stored as a serialized string,
thus you can even store arrays or objects in a registry entry – it’s
not recommended though. Using phpMyAdmin’s
The Registry API¶
There is an easy-to-use API for using the registry. Simply call the following code to retrieve an instance of the registry. The instance returned will always be the same, as the registry is a singleton:
use TYPO3\CMS\Core\Utility\GeneralUtility; use TYPO3\CMS\Core\Registry; $registry = GeneralUtility::makeInstance(Registry::class);
After retrieving an instance of the registry, you can access the registry values
get() method. The
get() method provides an
interesting third parameter to specify a default value that is returned if the
requested entry is not found in the registry. This happens, for example, the
first time an entry is accessed. Setting a value is also easy with the
$namespace : namespace in which the value to set
$key : the key of the value to set
$value : the value to store
|Represents an entry’s namespace. In general, the namespace is an
extension key that starts with
$namespace : namespace from which the value is to be obtained
$key : the key of the value to be retrieved
$defaultValue : a default value if the key was not found in the given namespace
|Used to get a value from the registry.|
$namespace : namespace from which the value is to be removed
$key : the key of the value to be removed
|Remove an entry from a given namespace.|
|removeAllByNamespace||$namespace : namespace to be emptied||Deletes all values for a given namespace.|
Do not store binary data in the registry, it it not intended for this purpose. Use the file system instead, if you have such needs.
Here’s an example taken from the Scheduler system extension:
use TYPO3\CMS\Core\Utility\GeneralUtility; use TYPO3\CMS\Core\Registry; $context = GeneralUtility::makeInstance(Context::class); $requestStartTimestamp = $context->getPropertyFromAspect('date', 'timestamp'); $registry = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(\TYPO3\CMS\Core\Registry::class); $runInformation = array('start' => $requestStartTimestamp, 'end' => time(), 'type' => $type); $registry->set('tx_scheduler', 'lastRun', $runInformation);
It is retrieved later using:
$registry = GeneralUtility::makeInstance(Registry::class); $lastRun = $registry->get('tx_scheduler', 'lastRun');