How to display errors on laravel 4?

Question

I'm trying to create an app on Laravel 4 beta but I can't debug it because it doesn't show any error, display_errors is on, error_reporting is E_ALL and debug => true (config/app.php). When I try to do an error on public/index.php it shows a parse error, but when I do it on the router it just shows a blank page (White screen of death). How can I fix this?

Thank you

Are you running on a local server environment? As far as I know, Laravel still checks to see if local or .dev appear in the URL before turning it into a local debug environment. — Mike Rockétt
– Mike Rockétt, Commented Jan 29, 2013 at 5:01
Oh, and what kind of error/exception are you throwing? Could you share that piece of code with us? — Mike Rockétt
– Mike Rockétt, Commented Jan 29, 2013 at 5:03
I'm having a similar problem, only that I get a generic 500 server error instead of screen of death. Error reporting works fine out of L4 — Matanya
– Matanya, Commented Feb 24, 2013 at 9:19
@Matanya - have you looked at your server logs to see WHAT the error 500 actually is? It could be any number of things... — Laurence
– Laurence, Commented Feb 26, 2013 at 6:17

Laurence · Accepted Answer · 2013-02-26 14:22:54Z

48

+50

@Matanya - have you looked at your server logs to see WHAT the error 500 actually is? It could be any number of things

@Aladin - white screen of death (WSOD) can be diagnosed in three ways with Laravel 4.

Option 1: Go to your Laravel logs (app/storage/logs) and see if the error is contained in there.

Option 2: Go to you PHP server logs, and look for the PHP error that is causing the WSOD

Option 3: Good old debugging skills - add a die('hello') command at the start of your routes file - then keep moving it deeper and deeper into your application until you no longer see the 'hello' message. Using this you will be able to narrow down the line that is causing your WSOD and fix the problem.

answered Feb 26, 2013 at 14:22

Laurence

60.2k22 gold badges178 silver badges215 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Jorre Over a year ago

I forgot to set the permissions on the app/storage folder even though the laravel intro states that clearly. Thanks!

Bruno Rodrigues Over a year ago

I keep seeing the WOSD with die('hello') in the first line of routes.php.. :(

Bruno Rodrigues Over a year ago

I've added a "files" statement to composer.json. This was the error... I still don't know what a I did wrong, but found the error.

cw24 · Accepted Answer · 2014-01-22 15:09:52Z

40

I had a problem with the white screen after installing a new laravel instance. I couldn't find anything in the logs because (eventually I found out) that the reason for the white screen was that app/storage wasn't writable.

In order to get an error message on the screen I added the following to the public/index.php

try {
    $app->run();
} catch(\Exception $e) {
    echo "<pre>";
    echo $e;
    echo "</pre>";
}

After that it was easy to solve the problem.

answered Jan 22, 2014 at 15:09

cw24

1,7432 gold badges22 silver badges31 bronze badges

1 Comment

mesqueeb Over a year ago

This solved my problem. I was linked here from: laracasts.com/discuss/channels/laravel/…

John Doe · Accepted Answer · 2014-10-23 14:24:37Z

22

Go to app/config/app.php

and set 'debug' => true,

answered Oct 23, 2014 at 14:24

John Doe

2212 silver badges2 bronze badges

Comments

Matanya · Accepted Answer · 2013-02-26 14:28:26Z

Following the good advice by @The Shift Exchange I looked at the error_log and indeed managed to solve to problem. it was simply a permissions issue:

Tue Feb 26 11:22:20 2013] [error] [client 127.0.0.1] PHP Fatal error:  Uncaught exception 'UnexpectedValueException' with message 'The stream or file "/Users/matanya/Sites/indgo/app/start/../storage/logs/log-apache2handler-2013-02-26.txt" could not be opened: failed to open stream: Permission denied' in /Users/matanya/Sites/indgo/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:71\nStack trace:\n#0 /Users/matanya/Sites/indgo/vendor/monolog/monolog/src/Monolog/Handler/RotatingFileHandler.php(77): Monolog\\Handler\\StreamHandler->write(Array)\n#1 /Users/matanya/Sites/indgo/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(37): Monolog\\Handler\\RotatingFileHandler->write(Array)\n#2 /Users/matanya/Sites/indgo/vendor/monolog/monolog/src/Monolog/Logger.php(217): Monolog\\Handler\\AbstractProcessingHandler->handle(Array)\n#3 /Users/matanya/Sites/indgo/vendor/monolog/monolog/src/Monolog/Logger.php(281): Monolog\\Logger->addRecord(400, Object(ErrorException), Array)\n#4 [internal function]: Monolog\\Logger->addError(Object(ErrorException))\n#5 /Users/matanya/Sites/in in /Users/matanya/Sites/indgo/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php on line 71

Once I used chmod to apply less stringent permissions, all went back to normal.

However, I'm not sure that it answers the OP's question, as he was getting a blank screen rather than a server error.

Ashish Kakkad · Accepted Answer · 2015-08-31 13:52:32Z

2

Inside config folder open app.php

Change

'debug' => false,

to

'debug' => true,

edited Aug 31, 2015 at 13:52

Ashish Kakkad

23.9k13 gold badges108 silver badges140 bronze badges

answered Aug 31, 2015 at 13:39

Hasnat Safder

492 bronze badges

Comments

Grant · Accepted Answer · 2017-04-15 00:24:34Z

2

Further to @cw24's answer • as of Laravel 5.4 you would instead have the following amendment in public/index.php

try {
    $response = $kernel->handle(
        $request = Illuminate\Http\Request::capture()
    );
} catch(\Exception $e) {
    echo "<pre>";
    echo $e;
    echo "</pre>";
}

And in my case, I had forgotten to fire up MySQL.
Which, by the way, is usually mysql.server start in Terminal

answered Apr 15, 2017 at 0:24

Grant

6,3973 gold badges42 silver badges60 bronze badges

Comments

TheRealJAG · Accepted Answer · 2016-11-12 05:02:50Z

1

In the Laravel root folder chmod the storage directory to 777

answered Nov 12, 2016 at 5:02

TheRealJAG

2,11821 silver badges16 bronze badges

Comments

omitobi · Accepted Answer · 2017-01-23 09:52:42Z

1

Maybe not on Laravel 4 this time, but on L5.2* I had similar issue:

I simply changed the ownership of the storage/logs directory to www-data with:

# chown -R www-data:www-data logs

PS: This is on Ubuntu 15 and with apache.

My logs directory now looks like:

drwxrwxr-x  2 www-data   www-data 4096 jaan  23 09:39 logs/

answered Jan 23, 2017 at 9:52

omitobi

7,3543 gold badges39 silver badges55 bronze badges

Comments

Ajay Patel · Accepted Answer · 2013-03-28 17:10:25Z

0

https://github.com/loic-sharma/profiler this is good example for alternative to laravel3 debug bar.

answered Mar 28, 2013 at 17:10

Ajay Patel

79311 silver badges24 bronze badges

Comments

Rahul Hirve · Accepted Answer · 2017-12-25 02:45:12Z

0

Just go to your app/storage/logs there logs of error available. Go to filename of today's date time and you will find latest error in your application.

OR

Open app/config/app.php and change setting

'debug' => false,

To

'debug' => true,

OR

Go to .env file to your application and change the configuratuion

APP_LOG_LEVEL=debug

edited Dec 25, 2017 at 2:45

answered Dec 25, 2017 at 2:40

Rahul Hirve

1,16913 silver badges20 bronze badges

Collectives™ on Stack Overflow

How to display errors on laravel 4?

10 Answers 10

3 Comments

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

10 Answers 10

3 Comments

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related