Set of features to safely use PHP-Error on production environment #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ng the error in reportError. It might be used to use additional loggers, or to display a nice error page for non-development users.
php_error will still catch all errors, but will not print them if display_errors is disabled. the same applies to ajax debugging
…ill be cleaned. But outside buffers, like gz_output will be left in touch
…rors is disabled.
Conflicts: src/php_error.php
Conflicts: src/php_error.php
Conflicts: src/php_error.php
Conflicts: src/php_error.php
Now it's generally useless, as php_error requires php 5.3
error_log, error_log_format and error_log_time_format
Conflicts: src/php_error.php
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just a merge of all my features from the other pull requests with necessary small fixes to make them work together in concert.
Additionally, you get the printout of output until the failure, and support for CLI scripts.
If you want to have consistent and safe error handling across environments, remove
php_error.force_disabledon production server, and use'display_errors' = 0instead. You can also enable rich error messages during runtime, by usingini_set('display_errors', 1).This way, your users won't see extensive debug information. But you can log all errors in your framework using callbacks, or send yourself an email if you want. And you can display a pretty user-facing error page in case something happens.