[PHP_FATAL_ERROR] - Management of error display in case of PHP_FATAL_ERROR - Automated CI and tests verification may produce that type of error.
Requirements
In case a PHP_ERROR_FATAL would be triggered, it would be important to have a clear message if DEBUG is on within FD.
Descriptive title for this enhancement
Actual behavior
As example, during the automated testing triggered by a merge request or packaging deployment, PHP_ERROR_FATAL may occur and result in a total failure of running tests. Without knowing the real reasons of the error, it is hard to debug properly.
Expected behavior
A proper error message with the root cause of the problem is mandatory.
Step by step description of new behavior
In order to reproduce a PHP_FATAL_ERROR, first the variables within variables.inc in /include must be ON. (Is Always ON during tests executions with CI).
For example, if a path to an ICON image cannot be found, a PHP_ERROR_FATAL will be thrown. Resulting in the deletion of the PHP session.
The error message should be triggered before the deletion of the session and the automated reload page (message would disapear).
Benefits
Debugging time will be shorter as error message is reporting line and proper error message.
Possible Drawbacks
None