While the module catches Exceptions, it does not catch Errors, which albeit less common can still happen.
It is important to properly handle them, or we risk site versions in broken states, which we've seen in a few cases.
Throw an Error during the publishing (or unpublishing, archiving and restoring) and note how the changeset remains in an undefined, and fundamentally broken, state.
Catch Throwable instead of Exception.
The suggested patch also cleans up the handling in the different cases.
Testing.
None.
None.
None.
Active
1.0
Code
Issue #3508936 by marco: Errors are not properly caught
Automatically closed - issue fixed for 2 weeks with no activity.