Feature #3649

Caches should be flushed on package version number changes

Added by Robert Lemke over 12 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Must have
Assignee:
Category:
Cache
Start date:
2009-06-12
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

Usually when upgrading from one FLOW3 version to another the user will experience a PHP fatal error because some interfaces (or other code parts) changed which are not compatible with cached code (eg. the AOP proxy classes). Therefore we need a new cache which stores information about all active packages - as a start that could be simply the version number or even a hash of all version numbers. On initializing the cache framework, this information should be compared with the actual values and if they don't match all caches should be flushed.


Related issues

Related to TYPO3.Flow - Feature #3581: Site lock / code cache flushing mechanismResolvedRobert Lemke2009-06-05

Actions
Related to TYPO3.Flow - Bug #3240: AOP cache is not emptied if class file is deletedResolvedRobert Lemke2009-05-07

Actions
#1

Updated by Robert Lemke over 12 years ago

  • Status changed from New to Accepted
  • Assignee set to Robert Lemke
#2

Updated by Robert Lemke over 12 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r2645.

Also available in: Atom PDF