Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This project is not covered by Drupal’s security advisory policy.
This module is unsupported due to a security issue the maintainer didn’t fix.
If you want to use this module, your options are:
- Choose another, actively maintained module instead
- File an issue in the queue with a patch to fix the module and then contact the security team to have your version reviewed and the project handed over to you following the unsupported project process.
- Hire someone to fix the security bug so the module can be re-published and supported (Consider hiring companies listed in the Marketplace)
I am looking for a co-maintainer as do not have a lot of time and am the only one working on this at the moment.
8.x-1.x Branch
Bugsnag API v3
8.x-1.4 is current stable release (please report any bugs)
8.x-1.x-dev is under active under development
1.) Upgrade to Bugsnag API v3 using composer.json
2.) Configuration options to make logging uncaught exceptions optional.
3.) Send logger items to Bugsnag (levels to be logged are in the Admin form).
7.x-2.x Branch
Uses Bugsnag library 2.9.2
- Upgrades Bugsnag PHP library to v2.9.2
- Uses admin screen for entering API key
- Add Release Stage option to config screen
- Option to send Environment Data with each error
- Removes configuration/setup from settings.php
- Adds user tracking
- Checks for correct PHP version on install
Project information
Unsupported
Not supported (i.e. abandoned), and no longer being developed. Learn more about dealing with unsupported (abandoned) projects
1 site reports using this module- Created by langworthy on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
