Robert Walker wrote in post #975828: > > No AuthLogic or anything else involved. I'd check your session store > configuration against what I showed here. Good luck.
I have checked both the session store and the session migration. I can see no problems there. The way we migrated from 2.3 to 3.0 was to first create a new Rails 3 application and then copy in the .git directory from the original. We then reconciled all of the diffs. As far as I can determine, all of the cruft was left behind. I have no doubt that AR Session Store works in a new Rails 3 application without AuthLogic. But that is irrelevant. The entire issue revolves around getting AuthLogic to work with AR Session Store. I simply cannot get AR Session Store to work with our AuthLogic setup. I cannot discover why it works in Rails 2.3.8 and not in Rails 3.0.3. Presumably, AuthLogic sets session.session_id to some value somewhere. However, AL uses an attribute called session_id to keep track of multiple concurrent sessions for the same user and I wonder if there is some problem that practice introduced in Rails3. I have asked about this on the AL list when it first cropped up and I never received any reply. Does anyone here happen to use AL and AR SS together on a Rails 3 project? -- Posted via http://www.ruby-forum.com/. -- 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.
