Whoops, looks like something went wrong.

Hi @jasonb,

What is the version of Laravel are you using? 4.2 or 5?

If you are using Laravel 4.2 you need to edit the config/app.php file and change the debug = false to debug = true (change it when you put your project in a server). Alternatively you may use a local configuration file for it.

If you are using Laravel 5 you should edit your .env.example file and rename to .env and it should works fine.

Hope it helps you.

OK that did it! I am running 4.2. Should I run 5 since I am learning or stay with 4.2?

@jasonb - Get a head-start and switch over to Laravel 5 now. It'll officially be out at the end of the month, but there won't be many changes before them.

Take a look at version 5 first though, it's not for everyone (compared to version 4).

@JefferyWay Thank you for the heads up! Your videos are amazing. You honestly have a gift for teaching others and your ability to communicate through the video is the best I have ever seen. -J

I am not exactly sure how to install Version 5. I am guessing like this: composer create-project laravel/laravel your-project-name dev-develop --prefer-dist

@jasonb Yes, that's how to install it.

And the difference between the 4.2 and the 5.0 is that you can handle environments better using the .env file instead of creating a folder and duplicating files. In Laravel 5.0 you just rename .env.example to .env, change the environments variables and voilà.

Welcome @jasonb

I have been learning Laravel 4 for the last 6 months - before 5 was even conceived.

Personally I am going to stick to 4 for a while longer. 90% of the lessons are on 4, most of the add ons have not yet been ported, and it is It is stable. 5 will take a little while to get really bedded down. So I will probably move when we get to 5.1. As a learner I can't face dealing with code issues and I see quite a few enquiries for L5 on the forums.

But if Jeff thinks L5 is ready - who am I to argue.

Welcome to Laravel

@vincej Thanks for the advise. I am just trying to wrap my head around OOP. Too long have I been a procedural php programmer.

@jasonb,

Stick to 4.2 if you intend to earn a living using it in any meaningful way. It's broad, mature and heavily supported. 5.0 is more for people who know laravel inside out. They can debug for changes in laravel itself and update or contribute with complete understanding. Many people on this forum are at that level or close to it. @vincej's advice is pretty bang on. Upgrading is no biggie, and if you work with laravel at all, you'll be asked to deal with a lot of 4.x.x code. 95% of companies are probably still using that or an earlier version. After saying that, I should mention that that's one mans experience. There's an awesome quote i read and can't find that essentially says 134% of internet statistics are bullshit 83% of the time. Anyhow, take that 95% with a grain of salt.

-Roni

@jasonb - you and me both. Although I did some considerable time using CodeIgniter, however, I did not use it in in the "Laravel OOP Way" ... you will often hear Jeff refer to CodeIgniter Grads as needing a little bit of reeducation. Most of us seen to have come down from CI.

You should check out the OOP Bootcamp series ... it's very good as an intro into Laravel meathods.

Thanks for pretty info, I just beginning with laravel 5

The docs seem to be incorrect .env.php did not work for me whereas just .env worked for production.

Very good tutorial to fix the issue: http://www.phplab.info/categories/laravel/whoops-looks-like-something-went-wrong

I have tried all off the above and still nothing. any more suggestions? -edit my .env => debug = true -Grant 777 permission to the storage folder --sudo chmod 777 -R storage -Have you forgotten to run composer install? --composer install -php artisan config:clear -php artisan cache:clear -php artisan key:generate still a blank screen.

If it still doesn't work after trying all the suggestion, TRY php artisan config:cache Important Note!! "php artisan cache:clear and php artisan config:clear one after another did not work"

Src: https://bobcares.com/blog/laravel-something-went-wrong/