uninitialized constant Sprockets::SassCacheStore

[sadiqmmm]

Error: uninitialized constant Sprockets::SassCacheStore

compass-rails gem is not capable with sprocket 3.0 rails 4.2.

As Compass-rails is the compatibility gem for chosen rails gem

[sadiqmmm]

Please update this gem with compass-rails dependency to v2.0.4 w/ rails 4.2 support.

Thanks

[buenaventure]

+1

[Streek]

You can fix this by upgrading compass to master which supports the new sprockets

gem "compass-rails", github: "Compass/compass-rails", branch: "master"

[victorlcampos]

+1

[qpowell]

+1

[vanboom]

+1 upgrading to the master branch did not solve this issue

[qpowell]

I ended up just forking it, updating the dependencies in my fork, and referencing that in my gemfile with: gem 'chosen-rails', git: 'git://github.com/qpowell/chosen-rails.git'.

Obviously, you may not want to do this in your project depending on what other dependencies you have, but it's an option.

[heberuriegas]

+1

[FlavienBusseuil]

+1

[chardos]

+1

[henriquecf]

+1

[goldnuggets24]

+1

[Saworieza]

+1

[tsechingho]

The related compass-rails issue is Compass/compass-rails#236.

As @Streek said, compass-rails master is working with sprockets 3.x.

But it's safe to use a dynamic gem dependencies for compass-rails.

Here is chosen-rails 1.4.2 to deal this issue.

Sorry for my lazy work. Thanks all of you.

[nihtalak]

+1

[Deleted user]

+1

[luapearth]

+1

[contradictioned]

But still compass 2.0.4 is not compatible with the current sass version:

In snapshot (Gemfile.lock):
  sass-rails (= 5.0.3)

In Gemfile:
  chosen-rails (~> 1.4.2) ruby depends on
    sass-rails (>= 3.2) ruby

  chosen-rails (~> 1.4.2) ruby depends on
    compass-rails (>= 2.0.4) ruby depends on
      sass-rails (<= 5.0.1) ruby

  sass-rails (~> 5.0) ruby

(not a chosen-rails problem, just wanted to report in case anybody else has this problem)

[yayayahahaha]

I use solution of @Streek , which is

gem "compass-rails", github: "Compass/compass-rails", branch: "master"

then

$bundle update.

and the final step is, restart the server.
and the final step is, restart the server.
and the final step is, restart the server.

it's important that I have to say three times.
thanks a lot.

[benwoodward]

@yayayahahaha bundle update is risky, as it'll update all your dependencies which can cause things in your application to break. Ideally one should have dependencies tied down to a version, e.g. ~> 5.5 to avoid this issue, but still.

bundle install will recognise the change and update the respective dependencies without touching everything else.

[iurifq]

Version 2.0.5 of compass-rails seems to fix the issue.

[abrambailey]

I removed compass-rails completely and still saw this error

[sidazhou]

+1 on @yayayahahaha

[danpe]

+1

[shicholas]

+1 this is still an issue, updating to the master branch of compass-rails seems to be working for me.

[Frank004]

+1

[blmundie]

+1

[zacksiri]

+1

[tsechingho]

compass-rails 3.0 is out.
compass-rails is no longer a dependency from chosen-rails 1.5.1, please see readme.