Problems in initalization with Rails 3.0.3, doesn't find ActiveRecord

[tarmotalu]

    /Library/Ruby/Gems/1.8/gems/default_value_for-1.0.1/lib/rails.rb:23: uninitialized constant ActiveRecord (NameError)
from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/all.rb:1:in `require'
from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/all.rb:1
from /Users/tarmot/Sites/clients/avor/office/config/application.rb:3:in `require'
from /Users/tarmot/Sites/clients/avor/office/config/application.rb:3
from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/commands.rb:21:in `require'
from /Library/Ruby/Gems/1.8/gems/railties-3.0.3/lib/rails/commands.rb:21
from script/rails:6:in `require'
from script/rails:6

[e10jon]

I have the same problem, but it only occurred after adding the gem 'cells' to my Gemfile. I'm on Rails 3.0.3.

[johnmaxwell]

I'm on Rails 3.0.4 and this happens to me when I have the acts_as_audited 2.0.0.rc7 and default_value_for in my gemfile. Separately, they both work fine. You can easily replicate the problem by making a boilerplate Rails app, making the Gemfile look like https://gist.github.com/edd2f596a5e9ff11b880 , and trying to open the rails Console.

    $ rails c
    /opt/local/lib/ruby/gems/1.8/gems/default_value_for-1.0.1/lib/rails.rb:23: uninitialized constant ActiveRecord (NameError)
from /opt/local/lib/ruby/gems/1.8/gems/railties-3.0.4/lib/rails/all.rb:1:in `require'
from /opt/local/lib/ruby/gems/1.8/gems/railties-3.0.4/lib/rails/all.rb:1
from /Users/john/trash/config/application.rb:3:in `require'
from /Users/john/trash/config/application.rb:3
from /opt/local/lib/ruby/gems/1.8/gems/railties-3.0.4/lib/rails/commands.rb:21:in `require'
from /opt/local/lib/ruby/gems/1.8/gems/railties-3.0.4/lib/rails/commands.rb:21
from script/rails:6:in `require'
from script/rails:6

Maxwell:trash john$

[ajh]

I think the problem is the presence of rails.rb inside lib.

My understanding is that when rubygem loads default_values_for it adds 'default_values_for/lib' to the ruby load path. Then when someone tries to "require 'rails'" they may get 'default_values_for/lib/rails.rb' instead of the expected 'rails/lib/rails.rb' (depending on the order of the load paths).

Maybe rails.rb could be moved into a subdirectory?

[AndrewO]

I had the same problem and am using the 'cells" gem as well. I've forked and removed the offending file: https://github.com/AndrewO/default_value_for

Although it's kind of hacky, I'm kind of reluctant to spend time figuring out how Rails 2 initializes gems since I just don't need it. Still, it makes me a little nervous, but I'm starting to wonder is Cells is doing something funky. Maybe I'll end up looking into it later.

[FooBarWidget]

This should be fixed in commit 999ba35. Can anybody confirm?

[ajh]

This commit isn't working for me with rails 3.0.5.

I'm able to get it to work by manually requiring 'default_value_for/railtie' in my config/application.rb below the Bundler.require line so the railtie seems to be defined correctly. I think what is missing is a 'lib/default_value_for.rb' file that requires 'lib/default_value_for/railtie' when the constant 'Rails::Railtie' is defined. Something like this maybe?

# in file lib/default_value_for.rb
require 'lib/default_value_for/railtie' if defined? Rails::Railtie

I might even go further and:

1. move lib/default_value_for/core.rb back to lib/default_value_for.rb,
2. put the above require at the top of the file, and
3. remove the require from init.rb

I'll test this and submit a pull request.

[ajh]

I sent a pull request here: #13

[FooBarWidget]

Thanks, I've merged your pull request. Can anybody else confirm that this works on Rails 3 as well as Rails 2? As soon as I have these two confirmations I will release.

[AndrewO]

I'm using 1bc2825 on a Rails 3 project right now. I'm not getting the problem I was having earlier, so I think the Rails 2/3 initialization bug has been sorted out. (I'm having a different problem, but I think it's unrelated or may just be my fault.)

[mlitwiniuk]

With 'cells' gem attached in Gemfile this problem still occurs.

[FooBarWidget]

I've confirmed that the problem is fixed. mlitwiniuk, if please open a separate bug report with details if you're still experiencing problems.