How to display errors on laravel 4?

debugging laravel error-reporting laravel-4
Blue Genie picture Blue Genie · Jan 28, 2013 · Viewed 109.6k times · Source

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

Answer

Laurence picture Laurence · Feb 26, 2013

@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.

Related questions

I can't turn off debug bar in Laravel on production

I have set 'enabled' = false in both package and in config/debugbar.php I cleared cache with php artisan cache:clear but I still see it on production environment. I accidently commited 'enabled' = false by accident and can't turn it …

Read More
PHPstorm - Unable to set breakpoints in blade.php files

I'm working on a Laravel application and can debug my controller php files fine, but Id like to also debug the blade.php files. With my current setup Ive followed all of jetbrains recommend settings for Laravel, (https://confluence.jetbrains.…

Read More
How do I remedy "The breakpoint will not currently be hit. No symbols have been loaded for this document." warning?

A C# desktop application on the express edition worked, but then it didn't work 5 seconds later. I tried the following: Ensure debug configuration, debug flag, and full debug information are set on all assemblies. Delete all bin and obj folders …

Read More