> Well it looks like the core issue is that HashWithIndifferentAccess > became ActiveSupport::HashWithIndifferentAccess in rails 3. The > session is a serialized ruby object which somewhere is saying that it > contains an instance of class ActiveSupport::HashWithIndifferentAccess > and rails 2 is complaining that it doesn't know what that is. > From what you've said I'm not sure why it works the first time. It > could be that something on the second request is storing such a hash > or that a development mode class loading oddity means that initially > ActiveSupport::HashWithIndifferentAccess is able to find the top level > class. You may be able to solve this by defining > ActiveSupport::HashWithIndifferentAccess in your rails 2 app >
I'll give that a try and see if it works. Another thing I noticed was that rails3 sets a 'session_id' and rails2 sets a :session_id I don't know why they changed that. -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
