Bug #28525
Caches are not flushed after creating a package
| Status: | Resolved | Start date: | 2011-07-27 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | Package | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 beta 1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
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
Associated revisions
[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 4 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 4 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 30a409619aa7c0f4bd30e67fa0b86cdc850fee48.