TYPO3 Exception 1596980032¶
Note
Below, the TYPO3 community may have provided additional information or solutions for this exception. However, these may or may not apply to your particular case. If you can provide more information, you should come back here and add your experience and solution steps to this issue once you have resolved it.
General TYPO3 troubleshooting tips can be found in the section "Troubleshooting" of the menu, and live support is available in the TYPO3 Slack channel #typo3-cms. (See How to get your TYPO3 Slack account.)
To add your experience, click "Edit on GitHub" above and follow the "Edit on GitHub" workflow. Also check out our tip on Coding Style and reST.
InvalidArgumentException: A cache identifier was not set¶
When debuging the corresponding cache.definition might look like this:
'' => array('groups' => array('pages', 'all'))This error can break the backend and frontend.
Background¶
Before TYPO3 version 10 it was common that the variable $_EXTKEY was
replaced automatically by the extension key of the corresponding
extension.
This has changed and the variable either has to be defined or the extension key automatically applied.
As the variable $_EXTKEY was undefined, the array key for
the cache definition was empty.
The error was therefore caused by an incomplete extension-update.
Solution¶
Search in all extensions for usage of $_EXTKEY in the file
ext_localconf.php.
If the variable is used but not defined in that file, define it in the beginning or replace it by the extension key.