Project

General

Profile

Actions

Bug #28589

closed

Autoloader Cache is not updated

Added by Oliver Hader over 12 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-07-30
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The autoload registry contents are stored in a separated PHP level caching in TYPO3 4.6.
There are already several mechanisms to flush the cache, e.g. on installing a new extension.

However, during development (and also maybe during TYPO3 Source Updates) new classes in the registry files are not considered.

Now, there are several ways to solve that:
  • if we rely on the extension manager to flush the cache on updates, we just would need the cacheIdentifier contain e.g. the TYPO3 version number
  • if that does not help, we need a way to find out whether a registry file was modified (e.g. MD5 hash of that file)
  • if that all does not help or is too expensive, we could use a lifetime for those caches (of course does not help during development and patch reviewing)

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #28598: [Cache] Let NullBackend implement PhpCapableBackendClosed2011-07-30

Actions
Related to TYPO3 Core - Bug #28266: When an extension is installed or removed, the autoloader cache must be flushedClosed2011-07-17

Actions
Actions

Also available in: Atom PDF