Nitesh Apte - 2015-12-26 19:06:47 - In reply to message 3 from Gerry Danen
Just saw the method that you have changed. We actually don't need to explicitly set 'display_errors'. All the errors and exceptions will be handled by the class only. In case you set it, the error messages will be displayed twice:
1. Because of 'display_errors'
2. Because of the package
While working in production, changed the values accordingly in 'define.inc' file. I think it is better to set environment(development or production) from a configuration file. This is what I will do if it is production env:
MODE will be changed so that script doesn't exit and show some generic message. These two statements of ErrorExceptionHandler.php
will do it for me -
echo DEBUGGING === TRUE ? $webMessage : SITE_GENERIC_ERROR_MSG;
MODE == 'DEVELOPMENT' ? exit() : "";
Hope, I was able to make it clear.
Another biggest advantage of this package - In this one you can add custom codes for exception. Make sure when you create/use code for exception, it follow some rules. For instance, use code 888 for exceptions occured during database connectivity. So, in case after a month you want to check how many times there was database connectivity failures, you just need to search for 888 in your log file.