Skip to content

Latest commit

 

History

History
96 lines (62 loc) · 3.47 KB

errors.md

File metadata and controls

96 lines (62 loc) · 3.47 KB
Raw

Errors & Logging

Error Detail

By default, error detail is enabled for your application. This means that when an error occurs you will be showed an error page with a detailed stack trace and error message. You may turn off error details by setting the debug option in your app/config/app.php file to false. It is strongly recommended that you turn off error detail in a production environment.

Handling Errors

By default, the app/start/global.php file contains an error handler for all exceptions:

App::error(function(Exception $exception)
{
	Log::error($exception);
});

This is the most basic error handler. However, you may specify more handlers if needed. Handlers are called based on the type-hint of the Exception they handle. For example, you may create a handler that only handles RuntimeException instances:

App::error(function(RuntimeException $exception)
{
	// Handle the exception...
});

If an exception handler returns a response, that response will be sent to the browser and no other error handlers will be called:

App::error(function(InvalidUserException $exception)
{
	Log::error($exception);

	return 'Sorry! Something is wrong with this account!';
});

To listen for PHP fatal errors, you may use the App::fatal method:

App::fatal(function($exception)
{
	//
});

HTTP Exceptions

Exceptions in respect to HTTP, refer to errors that may occur during a client request. This may be a page not found error (404), an unauthorized error (401) or even a generated 500 error. In order to return such a response, use the following:

App::abort(404, 'Page not found');

The first argument, is the HTTP status code, with the following being a custom message you'd like to show with the error.

In order to raise a 401 Unauthorized exception, just do the following:

App::abort(401, 'You are not authorized.');

These exceptions can be executed at any time during the request's lifecycle.

Handling 404 Errors

You may register an error handler that handles all "404 Not Found" errors in your application, allowing you to return custom 404 error pages:

App::missing(function($exception)
{
	return Response::view('errors.missing', array(), 404);
});

Logging

The Laravel logging facilities provide a simple layer on top of the powerful Monolog. By default, Laravel is configured to create daily log files for your application, and these files are stored in app/storage/logs. You may write information to these logs like so:

Log::info('This is some useful information.');

Log::warning('Something could be going wrong.');

Log::error('Something is really going wrong.');

The logger provides the seven logging levels defined in RFC 5424: debug, info, notice, warning, error, critical, and alert.

Monolog has a variety of additional handlers you may use for logging. If needed, you may access the underlying Monolog instance being used by Laravel:

$monolog = Log::getMonolog();

You may also register an event to catch all messages passed to the log:

Registering A Log Listener

Log::listen(function($level, $message, $context)
{
	//
});