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 Cheung <[EMAIL PROTECTED]> wrote: > Sent from my iPhone > > On 13 Nov 2008, at 18:13, RichardOnRails <[EMAIL PROTECTED] > > > > > wrote: > > > 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 onhttp://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=' > > cache_template_extensions was a deprecated setting and has since been > removed. > > > 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_versio > > n” > > 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
