CODEWITHSUNDEEP
debugginglaravellaravel-4
suncoastkid
suncoastkid

Reputation: 2223

Laravel 4 debugging not working

It's extremely frustrating that I have 'debug' => true in the app config but all Laravel is showing is "Whoops, looks like something went wrong." For the love of coding, does somebody know how to get debugging to work?

Upvotes: 13

Views: 13779

Answers (11)

Kamal Behboudi
Kamal Behboudi

Reputation: 79

well you need to clear configuration cache and regenerate it each time you change config files

run 'php artisan config:cache' in console and your good to go

Upvotes: 0

Tanvir
Tanvir

Reputation: 1695

I have faced the same problem. Laravel was showing only "Whoops, looks like something went wrong." but this line and not showing the actual error. Then I have checked the app/config/app.php file and changed "debug" => false to "debug" => true and it worked perfectly.

You said that you have also done it and still not working. I suggest you to run a composer update command for your project and then try again.

Upvotes: 17

Andres Felipe
Andres Felipe

Reputation: 4330

I had the same problem several times and I have two possibilities.

  • the folder storage doesn't have the right permissions, you should use chmod 755 or chmod 777
  • the public/index.php has none permission or a 777

These two options has occurred to me before, maybe there are some more.

Upvotes: 0

Sidhannowe
Sidhannowe

Reputation: 475

To be sure your app is in development mode, edit bootstrap/start.php, in the detectEnvironment function simply put your machine name. On linux use hostname terminal commande to determine your machine name.

$env = $app->detectEnvironment(array(
  'local' => array('homestead', 'Jeanphi'),
));

Upvotes: 2

Makara Dewangga
Makara Dewangga

Reputation: 1

i got same problem with that... first, laravel run well on windows using apache.. then while i'm using ubuntu and nginx, it shows "Whoops, looks like something went wrong."

no error in php log and nothing found on laravel log..

so i tried modify path folder permission to 0777

sudo chmod -R 0777 {put your folder application folder here}

it works

Upvotes: 0

T0plomj3r
T0plomj3r

Reputation: 695

Had that same problem altought my app was in debug mode. In my case I was deploying on server,and to make that work you must take care of detectEnvironment variable.

It is located in bootstrap/start.php

$env = $app->detectEnvironment(array(

       'local' => array('your_server_name'),

));

as it's instructed in the docs :

http://laravel.com/docs/4.2/configuration

Upvotes: 0

yellow-saint
yellow-saint

Reputation: 934

I came across problem recently, after separating out debug and a few other config options into a separate (dev.php) config file.

The in-hindsight obvious, by-logic obscure solution: Don't move debug out of config/app.php

Upvotes: 0

Colin Hilbert
Colin Hilbert

Reputation: 69

Some changes need an apache restart to take effect.

Upvotes: 0

rockstardev
rockstardev

Reputation: 13527

For all it's worth, I was getting this error now after deployment because I didn't create these folders:

/app/storage/cache
/app/storage/logs
/app/storage/meta
/app/storage/sessions
/app/storage/views

Upvotes: 0

Andrew Downes
Andrew Downes

Reputation: 557

Check you haven't renamed your app/config folder as fideloper suggests in the comment.

For example you might have renamed it to prevent overwriting the default config settings when copying your site somewhere else.

Upvotes: 0

Antonio Frignani
Antonio Frignani

Reputation: 961

Actually debugging is working fine for me with L4.0.7 when i set 'debug' => true in app/config/app.php That switch tells Laravel to turn on Whoops and to bypass the 'compiled.php' file. When it is disabled, Whoops will not show. A normal server error page is served instead.

Were you expecting something else?

EDIT: maybe you are referring to "debugging" as the old profiler bar that were in L3 (Anbu). In that case I suggest you install this package

Upvotes: 1

Related Questions