Bug #29414: Deletion of packages results in fatal error - TYPO3.Flow - TYPO3 Forge

TYPO3 Flow Base Distribution TYPO3.Eel TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Welcome Packages Applications

Bug #29414

Deletion of packages results in fatal error

Added by Robert Lemke almost 4 years ago. Updated almost 4 years ago.

Status:

Resolved

Start date:

2011-09-01

Priority:

Must have

Due date:

Assigned To:

Robert Lemke

% Done:

100%

Category:

Command

Target version:

TYPO3 Flow Base Distribution - 1.0 beta 2

PHP Version:

Complexity:

Has patch:

Affected Flow version:

Description

Most package operations (package:delete, package:deactivate etc.) and possibly also flow3:cache:flush result in a fatal error like this one:

$ ./flow3 package:delete TYPO3.T3con11Typo3Org
Flushed all caches.

Fatal error: Call to a member function dispatch() on a non-object in /opt/local/apache2/htdocs/sites/flow3.org/Packages/Framework/TYPO3.FLOW3/Classes/SignalSlot/SignalAspect.php on line 49

Related issues

Associated revisions

Revision df34272c
Added by Robert Lemke almost 4 years ago

[BUGFIX] package:* commands no longer issue a fatal error

Most package:* commands and sometimes also the flow3:cache:flush
command issued a fatal error. The actual command was executed
successfully, but the SignalAspect caused a fatal error because
the proxy code cache had already been flushed and therefore
FLOW3 was in an unstable state.

Those commands which flush the code caches will now exit right away
to avoid any further code execution.

Change-Id: I8bbb9112cec12f1888e79896787db8a9d4e125a0
Resolves: #29414