Tweak Debug component for production #8281
Labels
Comments
|
@fabpot how it should be configured? Using bitmask? |
|
+1 it's good to have nice handling of php errors in prod environment |
|
@fabpot as Exceptions in the engine RFC declined for PHP 5.6 we must continue work on this ticket. Please describe how do you see it and I will work on the PR. |
This was referenced Sep 27, 2014
fabpot
added a commit
that referenced
this issue
Oct 3, 2014
…-grekas) This PR was merged into the 2.6-dev branch. Discussion ---------- [FrameworkBundle] enable ErrorHandler in prod | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #11053, #8281 | License | MIT | Doc PR | - - a new debug.error_handler service is the registered PHP error handler, with ErrorHandler::register() as factory - ErrorHandler::register() is patched so that it checks if the currently registered error handler is an instance of ErrorHandler - in which case it returns this instance and don't create a new one. - DebugHandlersListener now listen to ConsoleEvents and re-injects fatal errors within the $app->renderException code path - DebugHandlersListener also has a new $scream parameter to control is silenced errors are logged or not Commits ------- fac3cc4 [FrameworkBundle] register ErrorHandler at boot time 4acf5d3 [Debug] make screaming configurable 4d0ab7d [FrameworkBundle] enable ErrorHandler in prod
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
symfony/symfony-standard@e4806c3#commitcomment-3424405
The text was updated successfully, but these errors were encountered: