Project

General

Profile

Actions

Bug #23694

closed

[Caching framework] Improve error message if no frontend was defined for core caches

Added by Christian Kuhn about 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Should have
Category:
Caching
Target version:
-
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)


Related issues 5 (0 open5 closed)

Related to TYPO3 Core - Bug #21355: [Caching framework] Hardcoded frontends of core cachesClosedChristian Kuhn2010-08-07

Actions
Has duplicate TYPO3 Core - Bug #23840: config example for memcached in t3lib/config_default.php breaks TYPO3 BE + FEClosedChristian Kuhn2010-10-25

Actions
Has duplicate TYPO3 Core - Bug #23653: Upgrading to 4.4.3 using Memcache leads to a non-running systemClosedChristian Kuhn2010-09-30

Actions
Has duplicate TYPO3 Core - Bug #23687: Throws Exception "Class does not exist" in Front- and Backend using memcache and caching-frameworkClosedChristian Kuhn2010-10-07

Actions
Is duplicate of TYPO3 Core - Bug #27677: Caching Framework: use t3lib_cache_frontend_VariableFrontend as fallback frontendClosedXavier Perseguers2011-06-24

Actions
Actions #1

Updated by Christian Kuhn over 13 years ago

  • Status changed from Accepted to Closed
  • Target version deleted (0)

Problem is handled by #27677

Actions

Also available in: Atom PDF