Bug #28525

Caches are not flushed after creating a package

Added by Robert Lemke about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
Category:
Package
Start date:
2011-07-27
Due date:
% Done:

100%

PHP Version:
Has patch:
Complexity:

Description

After creating (or deleting, activating, deactivating) a package through the command line, the caches are not flushed. That can lead to interesting, but still unnecessary fatal errors.


Related issues

Duplicated by TYPO3.Flow - Bug #4118: Package Manager does not clear the code cache on activating / deactivating packages Resolved 2009-08-03

Associated revisions

Revision 30a40961 (diff)
Added by Robert Lemke about 8 years ago

[BUGFIX] Flush caches after changing package states

This adds a flush caches call to the end of all commands which affect
the package state (that is create, delete, activate and deactivate).

For this special case – modifying the code base during a script run –
it is necessary to exit early in order to prevent unforeseeable problems
with removed or altered code.

In the longterm the caches should also be flushed when the Package
Manager's API methods are used – but that's not in the scope of this
bug fix.

Change-Id: I173c7ed7ecefb9fb67f8e24c0e9a93e594105cfb
Resolves: #28525

History

#1 Updated by Mr. Hudson about 8 years ago

  • Status changed from Accepted to Under Review

Patch set 1 of change I173c7ed7ecefb9fb67f8e24c0e9a93e594105cfb has been pushed to the review server.
It is available at http://review.typo3.org/3802

#2 Updated by Robert Lemke about 8 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF