Do you have the correct permissions set on your storage folder? the web server needs write access to the storage folders
See: http://laravel.com/docs/4.2/installation#configuration
chmod -R 775 app/storage/
Did you turn off debug mode?
app/config/app.php
No, debug is set to true in app/config/app.php. I think it happens since i upgraded to Laravel 4.2 from Laravel 4.1
are there any app::fatal app::missing or app::error defs in your routes or filters?
It could be that some default one was created when you upgraded in the filters.php file or something and it is trying to render a custom error page and failing.
It doesn't work... It's very strange, because some errors are correctly displayed, and sometimes it's a white screen.
That is strange, is there a common denominator between the ones that work and the ones that don't?
Eg 500 errors work, 404s don't
Anything in the error log? It could be a server error
It seems that errors in views appear correctly, and errors in controllers, route or model don't appear.
However, it is possible to see this errors in the error log file of php.
That is strange... I almost wonder if there was an error in the upgrade or something. have you tried flushing cache and everything?
artisan cache:clear
artisan dump-autoload
composer dump-autoload
There may be others you can try. I am not sure what else you can try.
I tried all of them, but still the same... Too bas, i'm going with. Thank you all
A possible solution is removing laravel blade engine commented code... in your blade.php code. That worked for me.
Lemme know if that works for you guys.
I know this is probably little use to anyone now, but this happened randomly to me.
I got it fixed by re-downloading the repository from BitBucket.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast