Blade view not reflecting changes

Question

I am developing a Laravel(5.2.29) project in Windows environment and testing it on Chrome browser.

I have made some changes on a Blade file using atom text editor and then refreshed my page and noticed that suddenly it has stopped reflecting the changes (it's loading the old Blade file).

I've tried the following:

• Restarted the browser
• Clearing browser cache
• Running php artisan cache:clear
• Running composer dumpautoload
• Deleting the Blade file (and got a view not found error). Then created a new Blade file with the same name, with no content and refreshed the page.

No matter what, the code displayed on the browser is always the same (old) version and not the content of the Blade file.

How can I solve this issue?

Solution 1

In order to avoid the parsing of Blade files on each reload, Laravel caches the views after Blade is processed. I've experienced some situations where the source (view file) is updated but the cache file is not "reloaded". In these cases, all you need to do is to delete the cached views and reload the page.

The cached view files are stored in storage/framework/views.

Solution 2

Run this command from terminal

php artisan view:clear

Solution 3

If you use PHPStorm, uncheck Preserve files timestamps deployment option: https://stackoverflow.com/a/42534996/2453148

Solution 4

php artisan cache:clear
php artisan route:cache
php artisan config:clear
php artisan view:clear
rm -rf bootstrap/cache/*/*

• Delete Cache/OPcache from PHP (fpm) of your Nginx/Apache server.

Solution 5

Clear the cache and clear the cached blade files:

php artisan cache:clear
php artisan config:clear
php artisan view:clear

View more solutions

Comments

[Noob Coder]

this worked..i have deleted all the views under framework. thanks.

[Ashit Vora]

I tried the same but I still see old view's cached version.

[Harry Bosh]

Cache is actually empty for me

[danboh]

I have a similar situation, but it not only affects the views but the controllers as well. I believe the issue is related to the difference in time between the testing server and my laptop. Unfortunately I haven't been able to resolve it no matter what I do :(

[danboh]

Just as an update, I was able to resolve this issue by pointing both my development environment and the testing server to the same time server so both have the exact same time. Hope this helps

[rhand]

@danboh How did you point your development environment to the same time server?

[user3791372]

This is it for me - the problem only started when I started to use PHPStorm midway through a project so I knew it wasn't anything with laravel!

[Connor Leech]

If you do this you'll have problems in your app. Use php artisan view:clear instead

[Luís Cruz]

@ConnorLeech can you expand on that? What issues have you experienced with this? Thanks

[Connor Leech]

I was getting an error that the path to this directory not found and Laravel error screen. I recreated the directory manually but think using built in artisan commands to handle this is best practice. Related issue: github.com/laravel/framework/issues/7295

[Can Geliş]

This was it for me. service php7.0-fpm reload resolved the issue.

[Gabby]

@Michel please explain more. It does work as long as you will change file name to new name and back to the original name after refreshing your page.