config.assets.enabled=false results in a method_missing error on rails start

[robconery]

Steps to reproduce:

rails new my_site
...
open my_site/config/application.rb

Now edit "config.assets.enabled = true" to be false

Start the app with rails s

... boom:
active_support/whiny_nil.rb:48:in method_missing': undefined methodcontext_class' for nil:NilClass (NoMethodError)
sass-rails-3.1.4/lib/sass/rails/railtie.rb:61:in block in <class:Railtie>' railties-3.1.1/lib/rails/initializable.rb:30:ininstance_exec'
railties-3.1.1/lib/rails/initializable.rb:30:in run' railties-3.1.1/lib/rails/initializable.rb:55:inblock in run_initializers'
railties-3.1.1/lib/rails/initializable.rb:54:in `each'

[guilleiguaran]

I will fix this in sass-rails, for now you can comment sass-rails in your Gemfile

[robconery]

cheers thanks

[robconery]

Hmm - that didn't work either...

[guilleiguaran]

what backtrace are you getting after of disable sass-rails in your Gemfile and run bundle install??

[vijaydev]

Guillermo: I just tried this, disabling sass-rails leads to a successful server startup. You found out the cause?

[spastorino]

If you disable the asset pipelining you don't want to use sass-rails. Anyway this was raising an informative error since here rails/sass-rails@74c5e4e but was removed since rails/sass-rails@1df74b5.

/cc @josevalim

[Gerhardk]

I'm running on Jruby 1.6.4 and Rails 3.1.1
The asset pipeline is disabled but I need the sass-rails gem for the active-admin gem.

So what your saying is I need to enable the asset pipeline before I can use the sass-rails gem meaning then only can I use the active-admin gem

[guilleiguaran]

if active-admin needs sass-rails probably it requires also the asset pipeline enabled.

[nolastan]

I just upgraded from rails 3.1.0rc6 to rails 3.1 and I'm now encountering the same error whenever I run rails generate.

$ rails g model test
/Users/stan/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.1.0/lib/active_support/whiny_nil.rb:48:in method_missing': undefined methodcontext_class' for nil:NilClass (NoMethodError)

[tkuisma]

I got the same error when trying to get active_scaffold_vho work with JRuby 1.6.3 and Rails 3.1.1.
The project had been created with 3.0.10.

Eventually I created a new project with Rails 3.1.1 and carefully copied everything from the previous project, making sure that new asset pipeline configurations (from 3.1.1) were left intact. After this the server starts without this "undefined method context_class" error and e.g. active_scaffold finds the correct assets under /app/assets directories.

[ragrawal]

I encountered same error. After I comment out this line in application.rb the error was gone

Bundler.require(*Rails.groups(:assets => %w(development test)))

[capripot]

I confirm the bug and the ragrawl' solution works well.

[LucasLMartini]

Confirmed, turning off sass on the Gemfile fixed it

[simonharrer]

There is another very related problem. When creating a new rails app using

rails new test -S

specifying to NOT use sprockets, the Gemfile still contains the related packages of the asset pipline which results in the error above.

I propose to include a check whether sprockets is enabled or not and corresponding to the outcome to NOT include the three gems comprised by the asset group.

[guilleiguaran]

@simonharrer just sent a PR, see #3926