Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12
  1. #11
    BigDave's Avatar
    Join Date
    September 18, 2001
    Location
    WAR 757!
    Posts
    49,192
    It's happening now.




    Quote Originally Posted by Will Stewart View Post
    Others were experiencing this issue, and our programmer says that he just found and fixed a bug in his code.

    Let me know if you see it again, thanks.
    ----------------

    Make the most of every opportunity for doing good in these evil days.

    --Ephesians 5:16

  2. #12

    Join Date
    January 03, 2003
    Posts
    10,660
    Quote Originally Posted by Will Stewart View Post
    Others were experiencing this issue, and our programmer says that he just found and fixed a bug in his code.

    Let me know if you see it again, thanks.
    The issue I described is definitely still happening. It is periodic, which I suspect is something to do with the cookie expiration. The sequence I list above seems to solve it, because (I'm using an educated guess here) that forces the code to expire both the vB and the other side cookies. Then when you finally re-login you get fresh cookies for both sides and everything is happy. Happy that is, until one side of the other expires and then everything gets out of sink again.

    Typically a cookie would be used to (indirectly) track when a users last server interaction occurred. It appears to me that if i stay on the vB side for a 'long time' (maybe a day) without using anything else, I get logged out of chat/article side. So now the system says I'm logged in, but if I try to use the chat side I get some crazy behavior. On the free parts I get what Dave is describing. On the subscriber parts I get an infinite redirect loop. If I only use the chat/article side for a 'long time', then I get logged out of the vB side and see different odd behavior. In this instance, the vB side continually prompts me to login, but no matter what it will not accept my correct user name / password. No matter which side gets our of sync, the solution is always the same.

    1) Go to vB side, logout
    2) Go to chat side, login
    3) logout
    4) Login to either chat or vB side and it works until one side or the other expires

    This probably isn't precisely correct, but I suspect it's close (too many years of experience with issues like this) and this post would likely help your dev to track it down. Judging from your efforts to decouple vB from everything else, I'm guessing that when a user interacts with the vB side the tracking for the chat side is updated and vice versa.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •