Provides an error handler for PHP that can execute a stack of handlers for various purposes.
An error handler for PHP that allows for the execution of handlers and formatters for viewing and managing errors in development and production. Because we all make mistakes.
This library requires PHP 5.4 or later. One test is skipped against HHVM, but all others pass. BooBoo will support PHP 7 in a future release.
It is recommended that you install this library using Composer.
$ composer require league/booboo
BooBoo relies upon and requires the following dependencies:
psr/log- A PSR-3 compliant interface for logging.
No other dependencies are required. The maintainer recommends installing monolog for logging.
BooBoo is designed to help make development easier while providing an integrated solution that can be deployed to your production environment. BooBoo offers the following advantages:
Some solutions throw exceptions for all errors, causing every notice to become a fatal error. BooBoo doesn't do this.
Rather than raise an exception for non-fatal errors, we display the error to you in a way that makes sense and lets the
program continue running. An
E_NOTICE shouldn't become an exception.
The Runner object offers a method for forcing all errors to be blocking, should you wish to throw exceptions for more minor errors. This is turned off by default.
Because we don't throw an exception by default, we don't generate a stack trace for minor errors. This means BooBoo won't show up in your logs, and when it handles an exception generated elsewhere, it isn't appended there, either.
This solution is designed with logging in mind, so that you can plug and play a PSR-3 compliant logging solution in and
go. BooBoo is sensitive enough to log errors, warnings and notices as such; exceptions are logged as critical, and
E_DEPRECATED warnings are logged as info. Handlers run even if formatting is disabled, so your logging will
always be on, even in production.
We can't possibly think through all your use cases, but we know you can. That's why we use standard interfaces to make it easy to extend and enhance the BooBoo functionality. (We also love pull requests; please share your innovations!)
PHP is changing every year, and BooBoo will change along with it.
The main object that you need to instantiate is
League\BooBoo\Runner. This object takes care of setting the error
handler, as well as handling errors and exceptions. It takes optional arguments during construction for handlers and
<?php $runner = new League\BooBoo\Runner(); $runner->register(); // Registers the handlers
It's very important to call
Runner::register() or the object won't register itself as PHP's error handler.
When you're developing, you want to view errors in the browser. In order to do this, you must provide a formatter. Without a formatter, the system won't intelligently know how to display the errors. As a result, the Runner will throw an exception and won't register the error handlers.
The library ships with four formatters for your convenience:
HtmlFormatter- Formats errors just like PHP's error formatting.
HtmlTableFormatter- Formats errors and exceptions similar to Xdebug, wth a full stack trace, even for errors.
JsonFormatter- Perfect for displaying errors to an API.
CommandLineFormatter- Working with the command line? This will produce pretty command-line errors.
NullFormatter- This formatter simply silences all errors. You can pass this when display_errors = Off. Adding a formatter is easy:
<?php $runner->pushFormatter(new League\BooBoo\Formatter\HtmlFormatter());
There may be times that you want certain formatters to handle the formatting for particular errors, and others to handle the formatting for other error types. Formatters support this.
For example, if you want all errors of warning or higher to show in the browser, but errors that are below this level to be ignored, you can configure the formatters to handle this scenario as such:
<?php $html = new League\BooBoo\Formatter\HtmlFormatter(); $null = new League\BooBoo\Formatter\NullFormatter(); $html->setErrorLimit(E_ERROR | E_WARNING | E_USER_ERROR | E_USER_WARNING); $null->setErrorLimit(E_ALL); $runner->pushFormatter($null); $runner->pushFormatter($html);
Formatters and handlers are treated as a stack. This means that the last item in will be the first item out. This is very important when dealing with formatters that only handle certain errors!
For example, in the example above, we have one formatter limited to errors and warnings, and the other formatting all error types. If we insert the HTML handler first, it will be run last; this would cause the NullFormatter to format all errors, and we would get no output.
Regardless of whether or not you want to format the error (or even output it to the screen), you may want to handle it in some way, such as logging it. BooBoo provides a way to handle errors, and provides a built-in PSR-3 compatible logging handler.
You can implement the HandlerInterface to create your own handlers. Handlers are run regardless of whether or not display_errors is true. Unlike formatters, you cannot direct handlers to ignore certain errors; it's assumed that you can handle this with the services that handlers work through.
If you have identified a security issue, please email firstname.lastname@example.org directly. Do not file an issue as they are public!