Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cache always in use, very hard for CSS development

  • 1 reply
  • 3 have this problem
  • 7 views
  • Last reply by 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

Chosen solution

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,

Read this answer in context 👍 1

All Replies (1)

more options

Chosen Solution

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,