Working with Umbraco Cloud 8, it appears that css changes are deployed with some sort of delay compared to cshtml changes, which take effect immediately.
This is really --like REALLY-- annoying, as changes to my cshtml often rely on changes to my css to make sense.
My current workaround is to insert the new css directly in the cshtml files, as it then deploys in sync with the cshtml, but this is of course far from ideal.
Do any of you know of a proper fix for this "out of sync" issue with css and cshtml?
Did you ever find a fix for this? I'm about to copy / past the compiled CSS into the CMS as a workaround. You're doing it through the git deploy process right?
fix for delay in css deployment
Hi all
Working with Umbraco Cloud 8, it appears that css changes are deployed with some sort of delay compared to cshtml changes, which take effect immediately.
This is really --like REALLY-- annoying, as changes to my cshtml often rely on changes to my css to make sense.
My current workaround is to insert the new css directly in the cshtml files, as it then deploys in sync with the cshtml, but this is of course far from ideal.
Do any of you know of a proper fix for this "out of sync" issue with css and cshtml?
And no, it is not a browser cache issues :-)
Best wishes Jesper
Did you ever find a fix for this? I'm about to copy / past the compiled CSS into the CMS as a workaround. You're doing it through the git deploy process right?
I found a solution to bypass the cached css: Adding a ?v=1234567890 to the css links where 1234567890 is a random number generated on page load.
Upside: You always get a brand new version of the css. Downside: Benefits from caching css is gone.
Best Jesper
Just generate a random string with razor in the template?
One option is to go completely random and force load the css file on every page view, similar to this:
Another option is to manually add a version number, timestamp or simillar, similar to this:
With this option, make sure users load the most recent version of the css, without force loading on every page view.
is working on a reply...