Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Cache always in use, very hard for CSS development

  • 1 antwoord
  • 3 hebben dit probleem
  • 4 weergaven
  • Laatste antwoord van Benff

more options

Hello,

Very recently the way CSS changes are displayed changed : now I need to use "Command + Shift + R" EVERY TIME... in the past just reloading the page would show the modifications.

I've also detected that ClearCache extension doesn't work anymore, neither does CacheToggle. I suspect something has been changed in the way the cache is handled.

Any idea ? Using Command + Shift + R all the time just to see a CSS modification is a real pain in the butt and if every extension allowing me to disable caching don't work anymore I don't see any other solution.

Thanks,

Cheers,

PS : using FF 37.0.1 on OSX Yosemite

Hello, Very recently the way CSS changes are displayed changed : now I need to use "Command + Shift + R" EVERY TIME... in the past just reloading the page would show the modifications. I've also detected that ClearCache extension doesn't work anymore, neither does CacheToggle. I suspect something has been changed in the way the cache is handled. Any idea ? Using Command + Shift + R all the time just to see a CSS modification is a real pain in the butt and if every extension allowing me to disable caching don't work anymore I don't see any other solution. Thanks, Cheers, PS : using FF 37.0.1 on OSX Yosemite

Gekozen oplossing

OK SOLVED.

The culprit was Better Wordpress Minify plugin... which was still activated.

Somehow the changes I made weren't "compiled" by the plugin but forcing the refresh with Command + Shift + R solved the issue...

So it's solved I just need to disable this plugin during development.

Cheers,

Dit antwoord in context lezen 👍 1

Alle antwoorden (1)

more options

Gekozen oplossing

OK SOLVED.

The culprit was Better Wordpress Minify plugin... which was still activated.

Somehow the changes I made weren't "compiled" by the plugin but forcing the refresh with Command + Shift + R solved the issue...

So it's solved I just need to disable this plugin during development.

Cheers,