Success

User tests: Successful: Unsuccessful:

avatar phproberto
phproberto
11 Oct 2013
avatar phproberto phproberto - open - 11 Oct 2013
avatar phproberto phproberto - reference | - 11 Oct 13
avatar phproberto phproberto - merge - 11 Oct 2013
avatar phproberto phproberto - close - 11 Oct 2013
avatar mbabker
mbabker - comment - 11 Oct 2013

You should have never needed this line. When JFactory creates the session it is adding that expire option to the array. My gut tells me this PR is masking another deeply rooted issue if you need these lines in this file to have your session expire when Elin and I didn't when testing originally last night.

avatar phproberto
phproberto - comment - 11 Oct 2013

I can only confirm that session wasn't expiring and after applying this it does. This was tested by David, JM & me.

avatar mbabker
mbabker - comment - 11 Oct 2013

I stand by my gut feeling on this one. Something really doesn't feel right about it.

avatar brianteeman
brianteeman - comment - 11 Oct 2013

In my tests it worked exactly how the session expiry worked before the changes. The session does expire but you do get to see the last page you were on via direct link and only know the session has expired when you click somewhere

avatar beat
beat - comment - 12 Oct 2013

I have same "gut feeling" as @mbabker .

Could this deep rooted issue be related with the bug in 3.1.5 that when a session expired (in admin area at least) that it needed a second click to really expire (aka you could access 1 more page before the session really expired) ?

avatar garyamort garyamort - reference | - 2 Dec 13

Add a Comment

Login with GitHub to post a comment