Disable laravel error handler

Is there anyway to disable the laravel error handler all together?

I want to simply display standard PHP errors, not the Whoops, looks like something went wrong errors.

回答1:

Not without majorly violating the principles of the framework (which I'll tell you how to do below, if you're still interested).

There's a few things that make this difficult to accomplish. It's easy enough to unset the default error and exception handlers

set_error_handler(null);
set_exception_handler(null);

but that leaves you with two major hurdles.

The first is Laravel registers a shutdown handler as part of its bootstrapping, and this shutdown function will look for the last error, and if it was a fatal error, manually call the exception handling code. There's no easy way to un-register a shutdown function.

The second is, the main Laravel Application handler looks like this

#File: vendor/laravel/framework/src/Illuminate/Foundation/Application.php
public function handle(SymfonyRequest $request, $type = HttpKernelInterface::MASTER_REQUEST, $catch = true)
{
    try
    {
        $this->refreshRequest($request = Request::createFromBase($request));

        $this->boot();

        return $this->dispatch($request);
    }
    catch (\Exception $e)
    {
        if ($this->runningUnitTests()) throw $e;

        return $this['exception']->handleException($e);
    }
}

That is -- if you application code throws an exception, Laravel catches it here and manually calls the exception's handleException method (which triggers the standard Laravel exception handling). There's no way to let PHP handle a fatal exception that happens in your application, Laravel blocks that from ever happening.

The part where I tell you how to do what you want

All this means we need to replace the main Laravel application with our own. In bootstrap/start.php, there's the following line

#File: bootstrap/start.php
$app = new Illuminate\Foundation\Application;

Replace it with the following

ini_set('display_errors','1');
class MyApplication extends Illuminate\Foundation\Application
{
    function startExceptionHandling()
    {
        //do nothing
    }

    public function handle(Symfony\Component\HttpFoundation\Request $request, $type = HttpKernelInterface::MASTER_REQUEST, $catch = true)
    {
        $this->refreshRequest($request = Request::createFromBase($request));

        $this->boot();

        return $this->dispatch($request);
    }    
}

$app = new MyApplication;

The first thing we're doing is setting PHP's display errors ini to 1. This makes sure errors are output to the browser.

Next, we're defining a new application class that extends the real application class.

Finally, we replace the real Laravel $app object with an object instantiated by our class.

In our application class itself we blank out startExceptionHandling. This prevents Laravel from setting up custom exception, error, and shutdown callbacks. We also define handle to remove the application boot/dispatch from a try/catch. This is the most fragile part of the process, and may look different depending on your Laravel version.

Final Warnings

If the handle method changes in future version of Laravel this will break.

If custom packages rely on adding custom exception handlers, they may break.

I'd recommend staying away from this as anything other than a temporary debugging technique.

回答2:

Then set 'debug' => false, in \config\local\app.php file

<?php

return array(

    'debug' => false,

);

回答3:

In laravel 5 to disable debug, you just need to comment

//'debug' => env('APP_DEBUG'),

in \config\app.php file

回答4:

Exception handling is hardcoded into the Application class. You can override the classes in your bootstrap/start.php file:

class ExceptionHandler {
    public function handleException($exception) {
        throw $exception;
    }
    public function handleConsole($exception) {
        throw $exception;
    }
}

class MyApplication extends Illuminate\Foundation\Application
{
    public function registerExceptionProvider() {}
    public function startExceptionHandling() {}
}

$app = new MyApplication;

It should go without saying that this is definitely not encouraged.

回答5:

This will get you close. There might be a more proper way of doing this. It replaces Laravel's current exception handler with a single-method class. I haven't tested this, besides the basic route below, so you may need to add other methods to satisfy different situations.

class ExceptionHandler
{
    public function handleException($e)
    {
        echo $e;
        die;
    }
}

App::bind('exception', App::share(function($app)
{
    return new ExceptionHandler;
}));


Route::get('/', function()
{
    throw new Exception('Testing');
});

回答6:

In file .env, just change: