Question

I’ve got 3 Rails 3.2 applications using the gem jquery-ui-themes. jquery-ui-themes uses scss for the image-path helper.

It works great on two of my applications, but the 3rd doesn’t seem to compile the scss files in either development or production modes.

IOW, it sends this to the browser

 background: #fcfdfd url(image-path("jquery-ui/redmond/ui-bg_inset-hard_100_fcfdfd_1x100.png")) 50% bottom repeat-x;

whereas the two working apps properly send

 background: #fcfdfd url("/assets/jquery-ui/redmond/ui-bg_inset-hard_100_fcfdfd_1x100.png") 50% bottom repeat-x;

I’ve spent many hours trying to make the app that’s broken as similar to possible to the two working apps as I can, but it’s still failing.

My theory is that SASS is choking on something previous to redmond.css.scss. If so, there should be an error logged somewhere. Where do I find the error output from SASS?

Update:

I introduced a deliberate error into redmond.css.scss and I got a proper error dump. So I know that I’m correctly clearing the cache and actually running sass. Now to figure out why it’s ignoring the image-path directives.

Answer 1

If you’re looking for the answer for my real problem (image-path not working), make sure you have the proper Bundler.require line in your application.rb. The old Rails 3.0 doesn’t work.

replace:

# If you have a Gemfile, require the gems listed there, including any gems
# you've limited to :test, :development, or :production.
Bundler.require(:default, Rails.env) if defined?(Bundler)

with:

if defined?(Bundler)
  # If you precompile assets before deploying to production, use this line
  Bundler.require(*Rails.groups(:assets => %w(development test)))
  # If you want your assets lazily compiled in production, use this line
  # Bundler.require(:default, :assets, Rails.env)
end