Feature request #1213: Update backend to Rails 2.3.0 RC1

Comments

1. Greg Hurrell 2009-02-03T16:12:55Z

   Status changed:

   • From: New
   • To: Open

2. Greg Hurrell 2009-02-03T18:42:49Z

   See also:

   • http://guides.rubyonrails.org/2_3_release_notes.html
   • http://weblog.rubyonrails.org/2009/2/1/rails-2-3-0-rc1-templates-engines-rack-metal-much-more

3. Greg Hurrell 2009-02-03T19:26:45Z

   First batch of breakage to fix; this on firing up script/server and trying to access a page:

   DEPRECATION WARNING: protect_from_forgery only takes :only and :except options now. :digest and :secret have no effect. (called from app/controllers/application_controller.rb:5)
   DEPRECATION WARNING: Disabling sessions for a single controller has been deprecated. Sessions are now lazy loaded. So if you don't access them, consider them off. You can still modify the session cookie options with request.session_options.. (called from app/controllers/application_controller.rb:9)
   
   Processing ApplicationController#index (for 127.0.0.1 at 2009-02-04 01:22:20) [GET]
     Parameters: {"protocol"=>"https", "action"=>"index", "controller"=>"posts"}
   
   NameError (uninitialized constant ActionController::Caching::Sweeper):
     app/sweepers/post_sweeper.rb:1
     app/controllers/posts_controller.rb:5
   
   Rendered rescues/_trace (121.1ms)
   Rendered rescues/_request_and_response (42.2ms)
   Rendering rescues/layout (internal_server_error)

4. Greg Hurrell 2009-02-03T19:31:06Z

   Funnily enough all specs still pass.

   1015 examples, 0 failures, 23 pending

5. Greg Hurrell 2009-02-04T11:52:12Z

   Ok, fixed the deprecation warnings, and worked around the NameError exceptions. Not really sure why those are being thrown; have posted to the Rails group to see if anyone can shed any light on the issue. See: http://groups.google.com/group/rubyonrails-talk/t/323ff7ec2d95ee32.

6. Greg Hurrell 2009-02-04T20:34:57Z

   Status changed:

   • From: Open
   • To: Closed

Add a comment

Comments are now closed for this issue.