Upgrades to the PHP notifier

Kristine Pinedo in Features on July 20th, 2016

We’re excited to share an overhaul of the Bugsnag PHP notifier that includes major improvements designed specifically for modern PHP apps. Be sure to upgrade to take advantage of the new ease of use and customization options.

Here’s what’s new:

New unified way to modify all error reports

Changing variables in your error report before they’re sent is now more flexible as notify(), notifyException(), and notifyError() accept a callable that Bugsnag runs later. This allows you to modify any part of an error report in a consistent way. Take a look at our documentation to see how it works.

Namespaced library under Bugsnag

We’ve changed the names of the files to be more consistent with language standards and, as a result, shorter to type. The library is now namespaced under Bugsnag.

Transport handling with Guzzle

We’ve implemented Guzzle as the HTTP client for Bugsnag PHP. With the addition of this community standard, the Bugsnag PHP library is now smaller and focuses solely on crash detection while Guzzle handles HTTP transport concerns.

Laravel notifier update

We’ve upgraded the Bugsnag Laravel notifier to take advantage of these changes, so its extra powerful under the hood.

And finally, we’ve resolved all known bugs in both the Laravel and PHP libraries.

We’re excited about these changes because it makes the PHP library much easier to use, and we hope you and your team have a great experience with it.


To take advantage of these improvements, you’ll need to upgrade to v3 of the Bugsnag PHP library. There are changes you’ll need to make to your current setup, so please be sure to take a look at our upgrade guide. This notifier requires PHP 5.5 or higher, but you can still use v2 if you’re using an older version. v2 will continue to be maintained.

To read the full list of changes, please see our PHP Changelog. Learn more about Bugsnag’s automatic PHP error reporting.