Project

General

Profile

Actions

Bug #68123

closed

Broken extbase configurationManager 1st level cache

Added by Marc Bastian Heinrichs almost 9 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Should have
Category:
Extbase
Target version:
-
Start date:
2015-07-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Since merging fix for #59505 the configuration managers return of the configuration is broken a very special way. It could be validated with the news extension. A defined news detail page in the list plugin has no effect anymore.

Here is why:
Setting the configuration in the configurationManager results in a cleared 1st level cache. This is new since #59505.
Inside the widget rendering process the first getConfiguration call is done by the LocalizationUtility without a pluginName (coming from the TranslateVH). So no call to getContextSpecificFrameworkConfiguration, so no override from FF. This is cached then and used after for the later link rendering the LinkViewHelper from news, which knows nothing about the FF config.

So the main issue here is the 1st level cache key in AbstractConfigurationManager::getConfiguration that was basically changed with https://review.typo3.org/#/c/6362/

I would suggest to expand the cache key.

Actions

Also available in: Atom PDF