Forum: Ruby on Rails Upgrading 2.2 to 2.3: console broken, "uninitialized constant Module::ActiveSupport"

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
4a551074ddba4460f95d011c47190d0e?d=identicon&s=25 Henrik --- (malesca)
on 2009-03-22 12:15
(Received via mailing list)
Upgrading a Rails app from 2.2 to 2.3.2 (via 2.3.0). Got things
working in the browser, but script/console seems messed up in both
2.3.0 and 2.3.2:

$ script/console
Loading development environment (Rails 2.3.2)
/Library/Ruby/Gems/1.8/gems/rails-2.3.2/lib/initializer.rb:56:in
`env':NameError: uninitialized constant Module::ActiveSupport
/Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/
testing/deprecation.rb:49:NoMethodError: undefined method
`alias_method_chain' for Test::Unit::Error:Class
/Library/Ruby/Gems/1.8/gems/rails-2.3.2/lib/console_with_helpers.rb:
5:NameError: uninitialized constant ApplicationController
>> Rails.version
=> "2.3.2"
>> ApplicationController
NameError: uninitialized constant ApplicationController

Any ideas?
4a551074ddba4460f95d011c47190d0e?d=identicon&s=25 Henrik --- (malesca)
on 2009-03-22 13:05
(Received via mailing list)
On Mar 22, 12:14 pm, Henrik N <hen...@nyh.se> wrote:
> `alias_method_chain' for Test::Unit::Error:Class
> /Library/Ruby/Gems/1.8/gems/rails-2.3.2/lib/console_with_helpers.rb:
> 5:NameError: uninitialized constant ApplicationController>> Rails.version
> => "2.3.2"
> >> ApplicationController
>
> NameError: uninitialized constant ApplicationController
>
> Any ideas?

Poked around more. Turns out the culprit was using "10.years" inside
environment (setting config.action_controller.session[:expire_after]).

I can reproduce the issue by generating a new app and adding 'puts
10.years' to environment.rb (e.g. after config.time_zone).

One fix is to not use it there. Another is to explicitly require
'active_support'. Tried with Rails 2.2.2 and saw similar issues; in
upgrading to 2.3, :session_expires (which takes a Time) changed
to :expire_after (which takes an interval), so I had not noticed it
before.
This topic is locked and can not be replied to.