Project

General

Profile

Actions
Copy link

Bug #67411

closed

Remove left over cache_classes from configuration

Added by Christian Kuhn over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
7.3 (Packages)
Start date:
2015-06-11
Due date:
% Done:

100%

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

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #67212: Discard TYPO3 class loader in favor of composer class loaderClosed2015-05-30

Actions
Actions
Copy link
 #1

Updated by Gerrit Code Review over 9 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40167

Actions
Copy link
 #2

Updated by Christian Kuhn over 9 years ago

  • Status changed from Under Review to New

Scenario in my case:

I had a option "cacheDirectory" set to "/tmp" for cache_classes in LocalConfiguration. With the removal of the DefaultConfiguration to FileBackend in #67212, the now implicit definition of cache_classes falls back to DatabaseBackend where this option is invalid. This in turn throws exceptions for example in extension manager where a clearAllCache() is called that instantiates all caches and then stumbles upon this combination.

Actions
Copy link
 #3

Updated by Andreas Kienast over 9 years ago

  • Status changed from New to Under Review
Actions
Copy link
 #4

Updated by Christian Kuhn over 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF