CODEWITHSUNDEEP
laravelstacktrace
Sacha
Sacha

Reputation: 569

Why have my Laravel 4.2 stack trace pages changed?

I've recently installed a fresh copy of Laravel 4.2 for a new project.

I've turned on debugging in app/config/app.php, set up my local environment in bootstrap/start.php and turned debugging on in app/local/app.php.

For some reason, my stack trace pages have changed. I can't find anything about them having officially changed, there's nothing in the upgrade guide...

Here's a screenshot of what it looks like. It's almost like an addition onto the normal "something went wrong" page, not like the orange/grey stack traces I've become used to.

To check, I created a whole new test project and the proper stack trace (albeit a different colour) is displayed, like so.

What's going on?

Upvotes: 2

Views: 1042

Answers (2)

TunaMaxx
TunaMaxx

Reputation: 1769

I'm surprised you two were able to get the problem solved with artisan clear-compiled and composer update alone. Neither of those work for me.

After some troubleshooting, I found there are changes made in Laravel 4.2.2 and 4.2.3 that cause the Whoops page to go wonky. I've opened an issue at github.

Changes introduced in 4.2.2 make the stack traces look like the first @sanaco screenshot...

Laravel 4.2.2:

enter image description here

...then additional changes made in 4.2.3 make it look the second one:

Laravel 4.2.3

enter image description here

Upvotes: 1

The Alpha
The Alpha

Reputation: 146221

Just run following artisan command from your command prompt:

php artisan clear-compiled

It supposed to ran after installation (I had same problem).

Upvotes: 3

Related Questions