ErrorEmail plugin for CakePHP 3.x
, (*1)
The ErrorEmail plugin is designed to enhance CakePHP's error handling system by adding the ability to conditionally email the dev team when errors or exceptions are thrown by your application with useful debugging information such as:
* Exception/Error Url
* Exception/Error Class
* Exception/Error Message
* Exception/Error Code
* Client IP
* File and Line Number
* Stack Trace, (*2)
, (*3)
Table of Contents
Installation
You can install this plugin into your CakePHP application using composer., (*4)
Run the following command, (*5)
composer require ebrigham1/cakephp-error-email
```
You can then load the plugin using the shell command:
```sh
bin/cake plugin load -b ErrorEmail
Or you can manually add the loading statement in the config/boostrap.php file of your application:, (*6)
Plugin::load('ErrorEmail', ['bootstrap' => true]);
In your config/Bootstrap.php replace:, (*7)
use Cake\Error\ErrorHandler;
With:, (*8)
use ErrorEmail\Error\ErrorHandler;
In your src/Application.php replace:, (*9)
use Cake\Error\Middleware\ErrorHandlerMiddleware;
With:, (*10)
use ErrorEmail\Middleware\ErrorHandlerMiddleware;
Configuration
Default configuration:, (*11)
'ErrorEmail' => [
'email' => false,
'emailLevels' => ['exception', 'error'],
'emailDeliveryProfile' => 'default',
'skipEmail' => [],
'throttle' => false,
'throttleCache' => '_error_email_',
'skipThrottle' => [],
'toEmailAddress' => null,
'fromEmailAddress' => null,
'environment' => null,
'siteName' => null
],
'Cache' => [
'_error_email_' => [
'className' => 'File',
'prefix' => 'error_email_',
'path' => CACHE . 'error_emails/',
'duration' => '+5 minutes'
],
],
This configuration is automatically merged with your application specific configuration preferentially using any keys you define., (*12)
- email (bool) - Enable or disable emailing of errors/exceptions
- emailLevels (array) - The email levels that should be used to determine what errors/exceptions are emailed. Valid levels are ['exception', 'error', 'warning', 'notice', 'strict', 'deprecated']. Each level is used to capture the following exceptions/php errors:
- 'exception' - \Exception (all user/framework thrown exceptions)
- 'error' - \Error, E_PARSE, E_ERROR, E_CORE_ERROR, E_COMPILE_ERROR, E_USER_ERROR
- 'warning' - E_WARNING, E_USER_WARNING, E_COMPILE_WARNING, E_RECOVERABLE_ERROR
- 'notice' - E_NOTICE, E_USER_NOTICE
- 'strict' - E_STRICT
- 'deprecated' - E_DEPRECATED, E_USER_DEPRECATED,
- emailDeliveryProfile (string) - The email delivery profile (defined in config/app.php under the Email key) to use "default" is the default
- skipEmail (array) - An array of exception/error classes that should never be emailed even if they are thrown Ex: [Cake\Network\Exception\NotFoundException::class, Cake\Network\Exception\InvalidCsrfTokenException::class]
- throttle (bool) - Enable or disable throttling of error/exception emails. Throttling is only performed if its been determined the exact same exception/error has already been emailed by checking the cache. Errors/Exceptions are determined to be unique by exception/error class + exception/error message + exception/error code
- throttleCache (string) - The cache configuration to use for throttling emails, the default is using the file cache driver with a 5 minute duration
- skipThrottle (array) - An array of exception/error classes that should never be throttled even if they are thrown more than once within the normal throttling window Ex: ['App\Exception\FullfillmentException'] These should be exceptions/errors you always want an email about every single time even if it spams your inbox.
- toEmailAddress (string) - The email address to send these error/exception emails to, typically the dev team. This will override the to address provided by the email delivery profile if both are present.
- fromEmailAddress (string) - The email address these emails should be sent from ex: noreply@yoursite.com. This will override the from address provided by the email delivery profile if both are present.
- environment (string) - Optional, with the default template this will be placed in both the subject and the body of the email so its easy to identify what environment the email was sent from Ex: local/staging/production.
- siteName (string) - Optional, with the default template this will be placed in both the subject and the body of the email so its easy to identify what site the email was sent from.
Note: the skipLog key from Error in your config/app.php file is also used. Exception/Error classes that are in that list will not be emailed out as it is assumed if they aren't important enough to even log they shouldn't be important enough to receive an email about., (*13)
Important: If email => true you must provide a valid email delivery profile to the emailDeliveryProfile config key. Typically the default will work fine unless you've renamed your application's default email delivery profile. If your email delivery profile doesn't define a to address and a from address you must also define the toEmailAddress and fromEmailAddress config values. If throttle => true then throttleCache must also be a valid cache configuration. The default should work fine as long as you don't redefine throttleCache in your config., (*14)
A configuration exception will be thrown if the config is detected to be invalid with an explination of what is incorrect., (*15)
Basic Usage
Typically you define these keys in your config/app.php file:, (*16)
'ErrorEmail' => [
'email' => true,
'skipEmail' => [],
'throttle' => true,
'skipThrottle' => [],
'toEmailAddress' => 'devteam@yoursite.com',
'fromEmailAddress' => 'noreply@yoursite.com',
'environment' => 'production',
'siteName' => 'yoursite.com'
],
With this configuration you would get emails whenever any fatal error or exception happened on your site with detailed debugging information in the email. If say you had an error on a popular page that many users were hitting that error would only be sent to you once every 5 minutes for the duration of the error being in existence. If a different error was thrown as well you would get that error right away the first time but then again it would be throttled to a maximum of once every 5 minutes., (*17)
If you found that you were receiving a lot of emails for exceptions/errors that you can not do anything about for instance Cake\Network\Exception\NotFoundException you can simply add it to the skipEmail config and you will no longer be bothered with those exceptions., (*18)
If you want to throttle emails in general to avoid spamming your team, but you have some exceptions that you must always receive an email about then you can use the skipThrottle list. For instance maybe a customer has paid for something on your site, but you were unable to fulfill their purchase after they paid because it requires an API call to a service that was temporarily down. Then you can add the exception you throw in that instance to the skip throttle list. This will result in all exceptions aside from the exceptions you define in the skipThrottle list being throttled to only email once per every 5 minutes while your FullfillmentException will email you every single time it happens., (*19)
Advanced Usage
Overriding Views
The default plugin email templates can be overridden by creating your own template files at:
* src/Template/Plugin/ErrorEmail/Email/html/error.ctp
* src/Template/Plugin/ErrorEmail/Email/text/error.ctp
* src/Template/Plugin/ErrorEmail/Email/html/exception.ctp
* src/Template/Plugin/ErrorEmail/Email/text/exception.ctp, (*20)
Extending/Overriding Core Functions
In order to extend/override core functionality of this plugin you will have to create your own classes which extend this plugin's classes., (*21)
Advanced Installation
Create src/Traits/EmailThrowableTrait.php:, (*22)
<?php
namespace App\Traits;
trait EmailThrowableTrait
{
}
Create src/Error/ErrorHandler.php:, (*23)
<?php
namespace App\Error;
use App\Traits\EmailThrowableTrait;
use ErrorEmail\Error\ErrorHandler as ErrorEmailErrorHandler;
class ErrorHandler extends ErrorEmailErrorHandler
{
use EmailThrowableTrait;
}
Create src/Middleware/ErrorHandlerMiddleware.php, (*24)
<?php
namespace App\Middleware;
use App\Traits\EmailThrowableTrait;
use ErrorEmail\Middleware\ErrorHandlerMiddleware as ErrorEmailErrorHandlerMiddleware;
class ErrorHandlerMiddleware extends ErrorEmailErrorHandlerMiddleware
{
use EmailThrowableTrait;
}
Now that you have your own classes you will need to update your application to use them., (*25)
In your config/Bootstrap.php replace:, (*26)
use Cake\Error\ErrorHandler; // Or use ErrorEmail\Error\ErrorHandler;
With:, (*27)
use App\Error\ErrorHandler;
In your src/Application.php replace:, (*28)
use Cake\Error\Middleware\ErrorHandlerMiddleware; // Or use ErrorEmail\Middleware\ErrorHandlerMiddleware;
With:, (*29)
use App\Middleware\ErrorHandlerMiddleware;
Adding Arbitrary Logic to Skip Emails
In your src/Traits/EmailThrowableTrait.php add this function:, (*30)
protected function _appSpecificSkipEmail($throwable)
{
// Add any logic here to skip emailing throwables that requires more complicated checking
// than instanceof class provided by plugin config, return true to skip emailing, false to not skip emailing
}
Adding Arbitrary Logic to Skip Throttling
In your src/Traits/EmailThrowableTrait.php add this function:, (*31)
protected function _appSpecificSkipThrottle($throwable)
{
// Add any logic here to skip throttling throwables that requires more complicated checking
// than instanceof class provided by plugin config, return true to skip throttling, false to not skip throttling
}
Overriding Emailing Functionality
In your src/Traits/EmailThrowableTrait.php add this function:, (*32)
protected function _setupEmail(\Cake\Mailer\Email $email, $throwable)
{
// Add logic here to pick the email template, layout,
// set the to address, from address, viewVars, ect.
// Make sure to return your email object at the end of the function
// so the plugin can send the email.
return $email;
}
Bugs and Feedback
http://github.com/ebrigham1/cakephp-error-email/issues, (*33)
License
Copyright (c) 2017 Ethan Brigham, (*34)
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:, (*35)
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software., (*36)
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE., (*37)
Wallogit.com
