By default, Ignition and the Flare PHP client (if you're using Flare in a non-Laravel application) will always send all the exceptions and errors to Flare.
In the cases where you don't want all exceptions being sent to Flare, you can from now on filter the exceptions sent using a callback:
// in ignition
Flare::filterExceptionsUsing(
fn(Throwable $throwable) => !$throwable instanceof AuthorizationException
);
// in the flare-php-client
$flare->filterExceptionsUsing(
fn(Throwable $throwable) => !$throwable instanceof AuthorizationException
);
When a PHP error is thrown, you can now configure which levels of errors should be sent to Flare:
// in ignition
Flare::reportErrorLevels(E_ALL & ~E_NOTICE);
// in the flare-php-client
$flare->reportErrorLevels(E_ALL & ~E_NOTICE);
In this case, Flare will send all PHP's internal errors except E_NOTICE errors.
Continue reading
A critical PHP vulnerability: what we did and what you should do
A critical vulnerability in PHP was disclosed today. It lets an attacker run code on your server without logging in, on a PHP install with default settings. That’s about as bad as it gets.
Ruben
Introducing: Dark mode for Flare
We heard you, so here it is: a Dark Mode for Flare!
Dries
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates