We're updating the issue view to help you get more done. 

Module Deactivation Failures throw errors instead of catching nicely?

Description

If there is an error when deactivation or resetting modules, this stops the whole process.
We should think about trying to catch these errors and report them, Otherwise, a bad installed module cannot be de-activated or reset, without editing the module, and removing the bad code.

Maybe in Dev mode, we can throw this error, or show more detail, but I think this would be a useful improvement to dealing with Module Management

Status

Assignee

Unassigned

Reporter

Gavin Pickin

Labels

None

Components

Fix versions

Affects versions

4.0.0

Priority

Major