Files
spa-api/application/config/error.php

83 lines
2.6 KiB
PHP
Raw Normal View History

2011-10-05 18:32:48 -05:00
<?php
return array(
/*
|--------------------------------------------------------------------------
| Error Detail
|--------------------------------------------------------------------------
|
2011-11-02 21:27:43 -05:00
| Detailed error messages contain information about the file in which an
| error occurs, as well as a PHP stack trace containing the call stack.
2011-10-05 18:32:48 -05:00
|
| If your application is in production, consider turning off error details
2011-11-02 21:27:43 -05:00
| for enhanced security and user experience. The error stack trace could
| contain sensitive information that should not be publicly visible.
2011-10-05 18:32:48 -05:00
|
*/
'detail' => true,
/*
|--------------------------------------------------------------------------
| Error Logging
|--------------------------------------------------------------------------
|
2011-11-02 21:27:43 -05:00
| When error logging is enabled, the "logger" Closure defined below will
| be called for every error in your application. You are free to log the
| errors however you want. Enjoy the flexibility.
2011-10-05 18:32:48 -05:00
|
*/
'log' => false,
/*
|--------------------------------------------------------------------------
| Error Handler
|--------------------------------------------------------------------------
|
2011-11-10 22:46:01 -06:00
| Because of the various ways of managing errors, you get complete freedom
| to manage errors as you desire. Any error that occurs in your application
| will be sent to this Closure.
2011-10-05 18:32:48 -05:00
|
2011-11-10 22:46:01 -06:00
| By default, when error detail is disabled, a generic error page will be
| rendered by the handler. After this handler is complete, the framework
| will stop processing the request and "exit" will be called.
2011-10-05 18:32:48 -05:00
|
*/
2011-11-10 22:46:01 -06:00
'handler' => function($exception, $config)
2011-10-05 18:32:48 -05:00
{
2011-11-10 22:46:01 -06:00
if ( ! $config['detail'])
2011-11-02 21:27:43 -05:00
{
2011-11-10 22:46:01 -06:00
Response::error('500')->send();
2011-11-02 21:27:43 -05:00
}
2011-10-05 18:32:48 -05:00
},
/*
|--------------------------------------------------------------------------
| Error Logger
|--------------------------------------------------------------------------
|
| Because of the various ways of managing error logging, you get complete
2011-11-02 21:27:43 -05:00
| flexibility to manage error logging as you see fit. This function will
| be called anytime an error occurs within your application and error
| logging is enabled.
2011-10-05 18:32:48 -05:00
|
2011-11-10 22:46:01 -06:00
| You may log the error message however you like; however, a simple log
| solution has been setup for you which will log all error messages to
| a single text file within the application storage directory.
|
| Of course, you are free to implement more complex solutions including
| e-mailing the exceptions details to your team, etc.
2011-10-05 18:32:48 -05:00
|
*/
2011-11-10 22:46:01 -06:00
'logger' => function($exception, $config)
2011-10-05 18:32:48 -05:00
{
2011-11-10 22:46:01 -06:00
$message = date('Y-m-d H:i:s').' - '.$exception->getMessage().PHP_EOL;
2011-11-02 21:27:43 -05:00
File::append(STORAGE_PATH.'log.txt', $message);
2011-10-05 18:32:48 -05:00
}
);