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.
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.
In file
.env
, just change:To:
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
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
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 lineReplace it with the following
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 definehandle
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.
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.
In laravel 5 to disable debug, you just need to comment
in \config\app.php file
Exception handling is hardcoded into the
Application
class. You can override the classes in yourbootstrap/start.php
file:It should go without saying that this is definitely not encouraged.
Then set 'debug' => false, in \config\local\app.php file