After deployment of statamic update html templates use old statamic vendor assets

[toxsick]

Hey guys,

I've run into an issue with my test deployment a few times now that happens when a new statamic version is deployed. After the upgrade cp pages html loads old (pre-update) CSS and JS files (e.g. app-08f252f3.js instead of app-3423cfef.js). The new assets are definitely there in /vendor/statamic/cp/build/assets/, but for some reason, the HTML is stuck on the old ones.

I also tried clearing all kinds of caches, re-installing, etc, but the result is the same.

Screenshot for reference:

Any ideas on how to get the HTML to reference the updated assets? I am relatively new to the laravel world, perhaps this is something super obvious, but I tried to find similar existing issues and found nothing so far.

I can into more detail on how the deployment works (with deployer), but perhaps you guys know the answer right away.

Help would be much appreciated. Thanks!

[edalzell]

This is usually browser cache, or if you're using a proxy, the proxy cache, clear those

[toxsick]

Hey @edalzell, thanks for that info, I will check with the provider if there is a cache layer that I'm not aware of. I will add details here for someone facing similar issues in the future.

[toxsick]

OK for anyone having similar issues in the future, it was the php OPcache^^ Very obvious to a php person I guess. I think it depends on your hoster how you can clear it, but after clearing it the assets are referenced correctly.