Bug #103987
closedAdminPanel not working with deactivated caches
0%
Description
I have the following stettings for cache in Development Context:
$GLOBALS['TYPO3_CONF_VARS']['SYS']['clearCacheSystem'] = 1; foreach([ 'assets', 'core', 'hash', 'imagesizes', 'pages', 'pagesection', 'phpcode', 'rootline', 'extbase', 'ratelimiter', 'extbase_datamapfactory_datamap', 'extbase_object', 'extbase_reflection', 'extbase_typo3dbbackend_queries', 'extbase_typo3dbbackend_tablecolumns', 'fluid_template', 'l10n', 'tx_solr', 'tx_solr_configuration', 'adminpanel_requestcache', 'dashboard_rss', 'runtime', 'typoscript', ### News 'news_category', ] as $cacheKey) { $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$cacheKey]['backend'] = 'TYPO3\CMS\Core\Cache\Backend\NullBackend'; } foreach([ 'runtime', ] as $cacheKey) { $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$cacheKey]['backend'] = 'TYPO3\CMS\Core\Cache\Backend\TransientMemoryBackend'; }
Then i get the following error:
TypeError TYPO3\CMS\Adminpanel\ModuleApi\AbstractModule::setModuleData(): Argument #1 ($moduleData) must be of type TYPO3\CMS\Adminpanel\ModuleApi\ModuleDataStorageCollection, bool given, called in /app/vendor/typo3/cms-adminpanel/Classes/Controller/MainController.php on line 137
The problem is that in $data = $cache->get($requestId); $data is false if there is no cache, but $parentModule->setModuleData() only allows type ModuleDataStorageCollection
Adminpanel settings:
config.admPanel = 1 admPanel.enable { cache = 0 debug = 1 edit = 0 info = 1 preview = 0 publish = 0 tsdebug = 1 }
Updated by Eike Starkmann about 1 month ago
Ok i think i was my bad, maybe this can be closed. The problem is that i deactivated the adminpanel cache: * 'adminpanel_requestcache',*
But a more reasonable message would be nice here i guess.
Updated by Garvin Hicking about 1 month ago
- Status changed from New to Closed
Thanks for updating. Sadly changing the caches can have all sorts of "weird" impacts which will be hard to specifically address with distinct messages.
However maybe contributing this to the exception knowledge database would be a good pointer?
Closing this issue for now :)