From: Chris W. <chr...@gm...> - 2006-01-22 16:32:01
|
On 1/21/06, Antti V=E4h=E4kotam=E4ki <ant...@he...> wrote= : >... > It seems that this call happens when CTX->request->session contains a > hashref which is not tied. I'm not sure how we can end up in this kind > of a situation and I don't know a way to replicate the bug we are > getting, so I don't know how (if at all) I could add the needed > parameters to the _create_session-call. A session is just a non-tied hashref if there's an error fetching it from the datastore, which typically happens in the case of an expired session. The OI user shouldn't care if the session is tied or untied, to her it's just a hashref. And the idea is that if any new interesting keys are added during the request we then create a brand new session, copy the data into it, and store it as normal. Looking at it now I'm pretty sure that call on line 141 of SessionManager.pm should be changed from: my $new_session =3D $class->_create_session; to my $new_session =3D $class->create; since that method will create a new session if not given an ID. Try that change and see what happens. Chris |