Logged out sooner than expected

  • slapbox

    (@slapbox)


    6 years, 5 months ago

    I’m not sure how the logout time is being calculated, but I’m pretty sure I just had a tab that was open for not more than 5 minutes log me out with a 90 minute timeout set.

    Possibly due to inactivity in another tab – although I don’t think I had any other individual tab open for the timeout duration.

    Environment details:

    • No multi-role in use
    • W3TC (database caching disabled)

      Not sure what else might be a possible culprit. Can you explain how the timeout logic works at a high level? Is the logic that handles it on the front end, I assume? I might be able to piece a bit more together when this reoccurs if I know a bit more about how it works.

      I’ve had a few weirdnesses with the logout timer today it seems to me, though I haven’t specifically timed or observed it too terribly much, so it’s not a very scientific report.

    • This topic was modified 6 years, 5 months ago by slapbox.
Viewing 1 replies (of 1 total)
  • Plugin Author Deepen Bajracharya

    (@j_3rk)

    6 years, 5 months ago

    @slapbox

    If you open up multiple browser tabs then this might not work as expected sometime as that feature is not accurately done. Need to rework but no ETA and promises given.

    Timeout feature is a minute based action. Meaning that countdown is a minimum of 1 minute + 10 seconds extra for judging user if it’s inactive for certain duration and so on. Same for both front and back.

    With caching might cause issues in frontend but not on backend as cache is disabled for backend mostly unless something configured manually for such.

Viewing 1 replies (of 1 total)

The topic ‘Logged out sooner than expected’ is closed to new replies.