Actions
Bug #23694
closed[Caching framework] Improve error message if no frontend was defined for core caches
Start date:
2010-10-08
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
This is an SVN patch request.
Type: Bugfix
BT:
Branches: trunk, 4.4
Problem:
With issue #21355 we un-hardcoded the cache frontend settings for core caches. This now leads to an error if own core caches are defined and the frontend setting is missing. t3lib_div::makeInstance will then get an empty string as frontend class and just spits error "Class not found", without more infromation on what exactly went wrong. This makes this issue hard to track down.
Solution:
Throw a more meaningful error message in t3lib_cache if frontend defintion is missing.
(issue imported from #M15937)
Updated by Christian Kuhn over 13 years ago
- Status changed from Accepted to Closed
- Target version deleted (
0)
Problem is handled by #27677
Actions