PHP Fatal Error Illuminate\Exception\WhoopsDisplayer::display()

Same problem here, did you resolve this? Ah... http://stackoverflow.com/questions/34568505/laravel-artisan-migrate-fail

Yes, as the link points out this is not because of a composer update, but because of a php upgrade to 7. They changed error class names.

There is a temporary solution, and that is to remove the 'Exception' class requirements from those files, but modifying system files is never a good idea (especially in production), and can be overwritten the next time the package is updated.

It would be possible to replace the exception handlers yourself, but I have not yet found a pre-built solution to this.

I'm using Phpstorm Xdebug, it helps me in this situation with this old project. Php storm can show u exception message before u will take Whoops Display Error...

If you want to see the errors you can do one of two things. One, you can push your code to a server with PHP5.6 and see the error or two, (which I think is much easier) is to adjust one line of a system file (which @dmeganoski doesn't recommend for good reason). If you add a return $exception on line 226 in vendor/laravel/framework/src/Illuminate/Exception/Handler.php it will skip laravel's fancy formatting and the whoops displayer error and give you a plain text error that you can actually do something with.

    protected function callCustomHandlers($exception, $fromConsole = false)
    {
        return $exception; // add this line
        foreach ($this->handlers as $handler)
        {
            // If this exception handler does not handle the given exception, we will just
            // go the next one. A handler may type-hint an exception that it handles so
            //  we can have more granularity on the error handling for the developer.
            if ( ! $this->handlesException($handler, $exception))
            {
                continue;
            }
            elseif ($exception instanceof HttpExceptionInterface)
            {
                $code = $exception->getStatusCode();
            }

Again, not the best long term solution but good enough until I upgrade my API to Laravel 5.* which is compatible with PHP7. Remember, if you run a composer update, it's very likely this fix will be overwritten.

If you use @sundaybk solution with

return $exception;

laravel's missing route handler will stop working.

I see this is still getting attention, so for any of you that are still having issues with this, here is an updated version of the laravel/framework package that supports php7.

It has been updated to 4.2.19 despite the name.

https://github.com/jadz/laravel-framework-4.2.18-php7

You will need to simply add the following to your 'repositories' file to use this version instead

{
      "type": "git",
      "url": "https://github.com/jadz/laravel-framework-4.2.18-php7"
    }

Then, change the version of "laravel/framework" to "dev-master".

I have been using this in production for months with no issues.

I think you were supposed to run composer install rather than composer update. Have a look at semantic versioning it will help you understand the difference between composer install and composer update.

The previous comments worked for me, thanks. I added the return statement to :

File name: vendor\laravel\framework\src\Illuminate\Exception\Handler.php Method name : callCustomHandlers

protected function callCustomHandlers($exception, $fromConsole = false) { return $exception; // add this line foreach ($this->handlers as $handler) { // If this exception handler does not handle the given exception, we will just // go the next one. A handler may type-hint an exception that it handles so // we can have more granularity on the error handling for the developer. if ( ! $this->handlesException($handler, $exception)) { continue; } elseif ($exception instanceof HttpExceptionInterface) { $code = $exception->getStatusCode(); }

........

This solves the 'Whoops' error, but has the side-effect of getting not any error message displayed whenever an exception happens.

I solved this by adding the following right before the return line:

echo $exception;