CODEWITHSUNDEEP
ruby-on-railsrubycachingless
mokagio
mokagio

Reputation: 17471

Rails 3.1 .css.less caching error

I am quite new with Rails and I am having some irritating problems with caching of css files.

I have a .css.less file with imports inside it. It's the only stylesheet the app includes, so the other files get imported only once and by this unique stylesheet. One of those imported .css.less stylesheets seems to be cached somewhere, because does not change in the browser when I change it's source.

I can only see the changes I made if I change something in the root stylesheet.

I have the server in development mode, so the caching should be off. I have also used <%= stylesheet_include_tag "style", :cache => false %>

I tried with Chrome and Firefox, with and without clearing their cache too. Always the same result, if I work only on that file the css the page receives when reloaded doesn't have the changes...

I also stopped the server and rm everything in the tmp folder of the app. No changes.

I am using Rails 3.1 with Ruby 1.9.3, with the less-bootstrap-rails gem. Both the root stylesheet and the imported one have .css.less extension.

What am I missing?

Thank you!

Upvotes: 3

Views: 849

Answers (4)

bronson
bronson

Reputation: 6002

I had this on Rails 4.0.8, infuriating. The config changes mentioned above didn't help. Here's what seems to have fixed it for me:

  • Ensure NO FILES share a base name. For example, you have a reports.css.less and a reports.js.coffee? Doesn't matter if they're in the same directory or not. Rename or delete one of them. (I changed it to reports-styles.css.less).

  • Blow away your cache: rm -rf tmp/cache

  • Restart your Rails app.

This appears to be a decent fix but, since I don't know what's actually going on, this could be totally false and it's just working by coincidence now. Sorry this answer isn't more rigorous!

Upvotes: 3

Jorge
Jorge

Reputation: 11

I've just came across the exact same problem.

I found that if you rename your *.css.less file (the one with the imports inside) to *.less, then this weird cacheing problem gets resolved.

Upvotes: 1

ghoppe
ghoppe

Reputation: 21784

Add this to your config/application.rb

# Version of your assets, change this if you want to expire all your assets
config.assets.version = '1.0'

See more at: Ruby on Rails Guide: Asset Pipeline

Upvotes: 0

RyanWilcox
RyanWilcox

Reputation: 13972

This is an area where I think the asset pipeline is broken, but I don't think there's a good fix.

If I remember correctly, to get changes in files you've included/required in your .css.less file, you need to change the .css.less file itself.

Upvotes: 3

Related Questions