Bug #86372
closedCacheManager 'assets' cache is not configurable in ext_localconf.php
100%
Description
Since commit https://review.typo3.org/c/54020/ + followup https://review.typo3.org/54061 (released only in v9) it is no longer possible to configure the 'assets' cache in ext_localconf.php files.
The IconRegisty is loaded in backend mode and reads the configuration (caches from 'assets') during object construction.
IconRegistry is usually instantiated during ext_localconf.php (due to extensions registering icons),
and therefore create's the 'assets' cache during ext_localconf.php loading.
After CacheManager has created the assets cache once, it will never be recreated again,
when the final configuration is set, after all ext_localconf.php files have been loaded.
Updated by Gerrit Code Review about 6 years ago
- Status changed from New to Under Review
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58371
Updated by Gerrit Code Review about 6 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58371
Updated by Benjamin Franzke about 6 years ago
- Priority changed from Should have to Could have
Seems this is not a regression (introduced in v9).
The problem actually exists since the introduction of the 'assets' cache in https://review.typo3.org/42730
Updated by Gerrit Code Review about 6 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58371
Updated by Gerrit Code Review about 6 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58371
Updated by Gerrit Code Review about 6 years ago
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58371
Updated by Benjamin Franzke about 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset ad847e9b273f6117645b0fc51964401b174a4d2e.