Skip to content

bugsnag/bugsnag-magento

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

61 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Bugsnag Notifier for Magento

Warning: This notifier has been deprecated and will only be receiving critical bug fixes in the future

The Bugsnag Notifier for Magento gives you instant notification of errors in your Magento applications.

Bugsnag captures errors in real-time from your web, mobile and desktop applications, helping you to understand and resolve them as fast as possible. Create a free account to start capturing errors from your applications.

The Bugsnag Notifier for Magento supports Magento CE 1.9.0.1+ and PHP 5.2+. It may work on older versions of Magento, but it's untested.

You can always read about the plugin or download it from Magento Connect.

Learn more about monitoring and reporting Magento errors with Bugsnag.

Installation

Magento Connect (recommended way)

  1. Visit the module's page on Magento Connect
  2. Press "Install Now" and and follow the instructions.

Modman

cd <your-magento-project>
modman init
modman clone https://github.com/bugsnag/bugsnag-magento.git

Composer

{
  "require": {
    "magento/core": "1.9.0.1",
    "bugsnag/bugsnag-magento": "dev-master",
    "magento-hackathon/magento-composer-installer": "*"
  },
  "repositories": [
    {
      "type": "composer",
      "url": "http://packages.firegento.com"
    }
  ],
  "extra":{
    "magento-root-dir": "htdocs/"
  }
}

Manual

git clone https://github.com/bugsnag/bugsnag-magento.git
cp -R bugsnag-magento/src/* <your-magento-project>

Configuration

In your Magento admin panel go to System → Configuration → Advanced → Developer and find the Bugsnag entry. If you don't see the entry, just press Save Config: the command would refresh the cache and pick up Bugsnag.

If the orange button "Fire Test Event" is not visible, then go to System → Configuration → Developer → Template Settings and set Allow Symlinks to Yes. You can safely set it back to No if you don't need the button or if you worry about the potential security risks (the plugin will keep working).

To do

  • Magento 2 introduces a lot of exciting changes. Currently, we do not support them