# Upgraded to Rails 2.2.0 -- bringing up Mongrel now fails **URL:** \ **Category:** Rails\ **Created:** [November 13, 2008, 7:13pm UTC](https://www.ruby-forum.com/t/upgraded-to-rails-2-2-0-bringing-up-mongrel-now-fails/153237 "2008-11-13T19:13:48Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![RichardOnRails](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e0b2c6/32.png) [@RichardOnRails](https://www.ruby-forum.com/u/RichardOnRails)\ **Post date:** [November 13, 2008, 7:13pm UTC](https://www.ruby-forum.com/t/upgraded-to-rails-2-2-0-bringing-up-mongrel-now-fails/153237/1 "2008-11-13T19:13:48Z")
Installing Rails 2.2 I was running • Rails 2 (ver. 2.0.2, I think) • Gem (ver. 1.0.1) I upgraded to 2.2 with the following commands: gem update –system cd’d to the ruby-container directory gem install rails rails –v (yielded: 2.2.0) setenv -m rails\_gem\_version 2.2 (set the machine’s “rails\_gem\_version” to 2.2) echo %rails\_gem\_version% (yielded: 2.2) I had a partial app I created under Rails 2 working. (Rails 2.0.2, I think). Today, I ran: K:\_Projects\Ruby\_Rails\_Apps\Payroll\>ruby script/server I got: =\> Booting Mongrel (use ‘script/server webrick’ to force WEBrick) =\> Rails 2.2.0 application starting on [http://0.0.0.0:3000](http://0.0.0.0:3000) =\> Call with -d to detach =\> Ctrl-C to shutdown server \*\* Starting Mongrel listening at 0.0.0.0:3000 \*\* Starting Rails with development environment… Exiting K:/\_Utilities/ruby186-26\_rc2/ruby/lib/ruby/gems/1.8/gems/rails-2.2.0/ lib/initializer.rb:514:in `send': undefined method `cache\_template\_extensions=’ Possible mistakes I can think of: 1. I installed Rails 2.2 instead of merely updating the existing Rails 2.0.2 2. gen –v produces 1.3.1 — I don’t know if that’s a problem 3. I created a machine’s environment variable “rails\_gem\_version” and set it to 2.2 4. I change config/environment.rb alternately from RAILS\_GEM\_VERSION = ‘2.0.2’ unless defined? RAILS\_GEM\_VERSION to: – RAILS\_GEM\_VERSION = ‘2.2’ unless defined? RAILS\_GEM\_VERSION – RAILS\_GEM\_VERSION = ‘2.2’ – RAILS\_GEM\_VERSION = ‘2.2.0’ Thanks in advance for any ideas on what the problem may be, Richard ---
**Author:** ![RichardOnRails](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e0b2c6/32.png) [@RichardOnRails](https://www.ruby-forum.com/u/RichardOnRails)\ **Post date:** [November 13, 2008, 8:42pm UTC](https://www.ruby-forum.com/t/upgraded-to-rails-2-2-0-bringing-up-mongrel-now-fails/153237/2 "2008-11-13T20:42:23Z")
Have a look at this: > > > This commit deprecates unused ActionView::Base.cache\_template\_extensions option > …and adds a deprecation warning for those having it in env specific config files. > > Thanks to José Valim for pointing this out. ---
**Author:** ![RichardOnRails](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e0b2c6/32.png) [@RichardOnRails](https://www.ruby-forum.com/u/RichardOnRails)\ **Post date:** [November 13, 2008, 8:44pm UTC](https://www.ruby-forum.com/t/upgraded-to-rails-2-2-0-bringing-up-mongrel-now-fails/153237/3 "2008-11-13T20:44:44Z")
Sent from my iPhone On 13 Nov 2008, at 18:13, RichardOnRails \ wrote: > gem install rails > > `cache\_template\_extensions=’ cache\_template\_extensions was a deprecated setting and has since been removed. ---
**Author:** ![RichardOnRails](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e0b2c6/32.png) [@RichardOnRails](https://www.ruby-forum.com/u/RichardOnRails)\ **Post date:** [November 14, 2008, 6:31am UTC](https://www.ruby-forum.com/t/upgraded-to-rails-2-2-0-bringing-up-mongrel-now-fails/153237/4 "2008-11-14T06:31:24Z")
Hi Freddy and Frederick, Thanks for you responses. I see from the Github site that cache\_template\_extensions has been deprecated. An exhaustive search of rb/erb/rhtml files in my Ruby/Rails directory reveals that “cache\_template\_extensions” appears only in the non-2.2 versions of some Rails components. A search of my old Payroll app, now renamed to Payroll-1, showed only one instance of “cache\_template\_extensions” containment in Payroll-1\config\environments\development.rb. Sounds like that’s my culprit. I commented it out. Things are back to normal. I wonder if I should expect any more surprises. Perhaps I should start from scratch with Rail 2.2. Again thanks to both of you for your help. Best wishes, Richard On Nov 13, 2:43 pm, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)