On Rails 3.2.9, Passing :protocol > :relative to stylesheetlinktag adds an attribute to the link rather than forcing a relative path on the url. Without a way to force relative protocols I experience unexpected behavior when caching pages that are accessible through http and https. Looks like it was rc1 bug. Ive just switched on rails 3.2.0.rc2, and this problem has disappeared. stylesheetlinktag(sources) Object.stylesheetpath(source) Object Also known as: pathtostylesheet. Using only relevant assets with Rails 3.2 Sprockets LESS. Im a bit new to Rails, so far so good.In your application.html.
erb view you will have to link each css. < stylesheetlinktag "stylesheets/application" > < stylesheetlinktag "stylesheets/foo" Firstly, I was getting some nasty errors about pre-compilation and noticed that my individual css/js files had been minified into their application counterparts and so I changed their declarations in the ruby helpers to reflect this(< stylesheetlinktag "application" >). rails 3.2.1 stylesheet not loading?. ask.programmershare.com provides programming skills exchange about ruby-on- rails-3.2.1 for developers.Tania, thanks for your answer: but the following lines (in application.html.erb) : < stylesheetlinktag "application", :media > "all" >
tag for each source provided. Rails looks in public/stylesheets for these files by default, but you can specify a full path relative to the document root, or a URL, if you prefer. rails g controller Home index. And it created a new controller and view for me: Notice how there are two stylesheets, one "Application" and one "Home".Second, In your applications layout add the suggested stylesheetlink tag eg. Please see rubyonrails.