Bug #90140
closed
Exception "No cache in the specified group 'pages'" in 10.2.2
0%
Description
Hello,
we're just upgrading powermail for TYPO3 10. So we're working with a TYPO3 10.2.2 (tested with PHP 7.3 and 7.4)
Our development environment was used with
$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['cache_pages']['backend'] = \TYPO3\CMS\Core\Cache\Backend\NullBackend::class;
If you are developing in an extension based on extbase and you want to persist an object with
$this->anyRepository->add($object);
An exception is shown in frontend:
(1/1) #1390337130 TYPO3\CMS\Core\Cache\Exception\NoSuchCacheGroupException No cache in the specified group 'pages'
If the usage of $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['cache_pages']['backend'] is deprecated, you can close this issue, but I didn't find anything documented.
Alex
Updated by Georg Ringer almost 5 years ago
- Related to Task #88366: Streamline caching framework caches added
Updated by Georg Ringer almost 5 years ago
- Status changed from New to Closed
Hi Alex,
thanks for creating the issue. This has been introduced with #88366 which changed the name of the cache. I would propose to remove the dependency to the name and just use the configuration behinde
'frontend' => \TYPO3\CMS\Core\Cache\Frontend\VariableFrontend::class,
'backend' => \TYPO3\CMS\Core\Cache\Backend\Typo3DatabaseBackend::class,
'options' => [
'compression' => true
],
'groups' => ['pages']
I am closing this issue, if you got any questions, please get in contact with me via slack.
Updated by Benni Mack almost 5 years ago
Thanks Alex and Georg for this change.
This is the change documented - https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/10.0/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.html
Apparently our change might break extensions that re-configure caches. I thought about doing a migration, but we cannot e.g. alter AdditionalConfiguration.php, so this might get tricky. Maybe we could do a system status report or something along the lines to fix this? (if this would solve the issue, let us know, and we could create such an additional thing in TYPO3 Core)
Updated by Alex Kellner almost 5 years ago
Thx for your help guys - that already helped a lot.