Bug #59848
closedEM crashes with exception #1382276561 (missing extension)
0%
Description
The full description of the PHP exception is:
The package "a" depends on "b" which is not present in the system.
The situation (an unresolved dependency) may arise probably only from problems with the deployment (eg a gut submodule not updated, or a manual edited LocalPackages.pgp).
Once the system is in this state, the EM is not usable any more. Which means you cannot install extension "b" from within the TYPO3 BE. Dependency or not, the EM should not break with a PHP exception.
Updated by Susanne Moog over 10 years ago
- Status changed from New to Needs Feedback
In my opinion throwing an exception here is the sensible thing to do - if your deployment script "destroys" part of your installation, it is also the job of the script to fix it.
It should not be possible to get the same problems if you just use the extension manager / core methods - if it is that would indeed be a bug.
Updated by Alexander Opitz almost 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.