- Now requires PHP
8.2.0+
. - Now requires Craft
5.0.0+
.
- Add plugin settings warnings when set via the config file.
- Only admins are now allowed to access plugin settings.
- Fix being unable to modify blacklist items in the control panel settings.
- Now requires PHP
8.0.2+
. - Now requires Craft
4.0.0+
.
- Allow appropriate plugin settings to be set via
.env
variables.
- Fix settings page in control panel not working.
- Add
craft.bugsnag.handleException()
.
{note} The plugin’s package name has changed to
verbb/bugsnag
. Bugsnag will need be updated to 3.0 from a terminal, by runningcomposer require verbb/bugsnag && composer remove superbig/craft3-bugsnag
.
- Migration to
verbb/bugsnag
. - Now requires Craft 3.7+.
- Fixed namespace that causes PSR warning
- Added
craft.bugsnag.getBrowserConfig()
to get the config needed for the Bugsnag JS client
- Fixed passing empty
releaseStage
value
- Added ability to set metadata on the fly by calling
{% do craft.bugsnag.metadata({ order: 1234 }) %}
. Note that this has to be done before the frontend asset is included
- Upgraded the Bugsnag client to v7
- Fixed user reporting
- Added
getClient
method to service. This exposes the client to other plugins / modules. - Added
browserApiKey
for configuring frontend reporting
- Parse
browserApiKey
andserverApiKey
for env variables and aliases
- Fixed frontend Bugsnag asset to comply with the latest version of JS client
- Added asset bundle to capture JS errors in a more seamless fashion
- The plugin can now capture early initialization errors (if manually setup in
app.php
)
- Fixed error when no items were added to exceptions blacklist
- Fixed filters support
- Added exceptions blacklist (lets you ignore those 404 errors that clogs up your log)
- Added support for
appVersion
- Fixed check that passes user information to Bugsnag if set
- Fixed error when installing plugin through the console command
- Fixed api config key in config example
- Initial release