>
> 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
>
Just to follow up on this...
Your workaround worked but it only went so far. Now I am getting this error.
Session contains objects whose class definition isn\'t available.
Remember to require the classes for all objects kept in the session.
(Original exception: #{const_error.message} [#{const_error.class}])
I am not going to chase this down. Who knows what object it's
complaining about. I think I am just going to set a cookie and track
it on the other app. That part seems to be working OK.
I hope this saves somebody lots of work.
--
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.
