If i change styles.css, my changes don't work, even if i clear the cache (by drush or by the button "clear cache").

any suggestions?


lsergei’s picture

Same thing, subscribing.

Simple question I think, but still no answer :(

aschiwi’s picture

Status: Active » Postponed (maintainer needs more info)

that doesn't really make any sense. any steps to reproduce?

lsergei’s picture

aschiwi, no, any special steps needed. Any other theme is updated any time I change correspondent css file. Busy is still using original (cached? misplaced?) css.

It has to be a very simple solution to this but I still looking for it.

aschiwi’s picture

I downloaded and installed a plain Drupal and Busy. Activated busy and changed something in style.css. It works right away. Are you using aggregated css files? If so clear your caches. It's actually easy - you check the path to style.css and if you change something in that file and it doesn't show up then it must be a Cache problem. I doubt this is a theme problem.

nanharbison’s picture

I was having the same problem. I cleared the cache multiple times and nothing changed. I unchecked aggregating CSS and cleared the cache, nothing changed. I noticed that the color.css file that was being used was in default/files/color/color.css. Drupal 7 seems to move it there. I went back to the global settings on the appearance page and just clicked on Save configuration even though I didn't change anything, and that made Drupal add the changed color.css to the default/files/color/ location.
I don't get why this is set up this way. It took a long time to figure this out over several weeks. I had been going directly to the default/files/color/color.cc and making changes, but I think that will eventually be overwritten when I save configuration again.

nanharbison’s picture

So I had to do this again. I cleared the cache, unchecked and then re-checked the compress and aggregate files and cleared the cache in between. What worked was saving the configuration on the appearance page of the theme I am using.

Vagelis’s picture

Issue summary: View changes

I had the same problem after editing the style.css of bartik. I had to flush all caches in order to see the changes.

aschiwi’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

Closing this. Everyone please note that you should never ever edit any styles in a contrib or core theme. Instead, create a subtheme and add your changes there.

Gung Wang’s picture

I got this weird problem too:

– All changes work perfectly on my localhost and development server
– The new responsive CSS doesn't work well on the production
– The old responsive.css is always loaded on the home page
– The new responsive CSS doesn't work in Firefox, Chrome, Edge
– It works good in Opera

I tried all methods I could find on Drupal Forum to refresh the CSS:

– Disabled the "Aggregate and compress CSS files"
– Clear Drupal Caches
– Clear Browsers' caches
– Clear the Drupal /files/tmp/ folders
– Restarted the Apache web server httpd
– Deleted the file of responsive.css and checkout it again on the Linux server
-- vi responsive.css // edit the the new file on the production server: my new changes are there
-- When to view the source code, it still shows me the old code/file

Final solution

-- Edit the html.php.tpl
-- Changed the code

Old code:   <link rel="stylesheet" media="all" href="/sites/all/themes/kith/css/responsive.css?id=1" />
New code:   <link rel="stylesheet" media="all" href="/sites/all/themes/kith/css/responsive.css" />

-- Works

-- It must be the problem of "?id=1"

computer_jin’s picture


It doesn't work for me. I am already using without id.

Please see this.

print $theme_url; /css/responsive.css' type='text/css' media='all' />

Any other solution for this?

faruq1256’s picture


If your using Cloudflare, purge the cache from cloudflare to reflect the css changes. You can also set the page rules to Bypass the cache at cloudflare

Thank you
Faruq Shaik