Message of the day:
Welcome to SilverStripe | Current stable: https://goo.gl/C4F1T9 | Feature requests: https://goo.gl/EcQ34L | Community Forum: https://forum.silverstripe.org | StripeCon EU 2019! https://stripecon.eu
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
Every time I have looked it up, that is what people seem to recommend
@lerni Enabling "Disable Cache" under "Network" (in developer tools) is (I think) the recommended way to do this
browserSync is involved but it looks as it doesn't matter how I trigger the reload - pasting, typing, clicking once cached, it's hard to overcome unless I use tricks I don't want clients/visitor to use.
@Erik Elmehed has joined the channel
yeah true, true
well, JS on live should be cachebusted; isn't it by default? For frontend there is a hashpathextension that creates unique links to js files
i just feel doing stuff like that ends up "cheating" what a client would end up doing but i get why you would 😄
Firefox should not use caches with <shift> pressed while hitting the reload button. But TBH I often disable FF's cache on my dev environment