Problem upgrading from Rails 2.0.2 to 2.2.2

[Schalk Neethling]

Hey all,

I just upgraded a very simple rails based website from Rails 2.0.2 to
2.2.2. When I started up Mongrel however, I got the following error:

** Starting Rails with development environment...
ExitingC:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:530:in
`send': undefined method `cache_template_extensions=' for
ActionView::Base:Class (NoMethodError)
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:530:in
`initialize_framework_settings'
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:529:in
`each'
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:529:in
`initialize_framework_settings'
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:526:in
`each'
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:526:in
`initialize_framework_settings'
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:154:in
`process'
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in
`send'
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in
`run'
... 29 levels...
from
C:/InstantRails/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from ./script/server:3
from -e:2:in `load'
from -e:2

Any help and pointers appreciated,
Schalk

[Schalk Neethling]

Hi All,

I found the following discussion on the group:
http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/ba1942467c19ea41/7b0a6ae9e87e8d49?hide_quotes=no

I now see this is a deprecated and now removed attribute. However, what
I was wondering, isn't running rake rails:update supposed to fix these
issues. From Aptana it states that rails:update does the following:

Update both configs, scripts and public/javascripts from Rails

Seeing that the files that contained the removed attribute is in the
config/environments folder I find it strange that the Rake command did
not fix it or, am I misunderstanding what exactly the command does?

Thanks,
Schalk

[Frederick Cheung]

On Nov 22, 10:10 am, Schalk Neethling <volume4.sch...@gmail.com>
wrote:

> Hi All,
>
> I found the following discussion on the group:
>

> I now see this is a deprecated and now removed attribute. However, what
> I was wondering, isn't running rake rails:update supposed to fix these
> issues. From Aptana it states that rails:update does the following:
>
> Update both configs, scripts and public/javascripts from Rails
>
> Seeing that the files that contained the removed attribute is in the
> config/environments folder I find it strange that the Rake command did
> not fix it or, am I misunderstanding what exactly the command does?

editing a user editable and often heavily modified file like
production.rb would be somewhat error prone. As far as I can remember
the only such file that is updated is boot.rb (which has a warning at
the top saying 'don't change me')

Fred

[Xlash]

The following command is deprecated in Rails 2.2.2
in config/environments/development.rb
config.action_view.cache_template_extensions = false

Regards,

Guillaume