Logging out troubles

[andrewK]

If you find yourself unable to logout, there is help! Due to changing the domain of the cookies that vBulletin sets to .rakeback.com (to support the multiple languages) from www .rakeback.com many may find that they are unable to logout.

To fix this, you must delete the offending cookies. My advice is to just delete all cookies associated with the rakeback.com domain. For help on deleting cookies for your specific browser, please see here: How to delete cookies

If anyone is still having trouble, please post here and I will help you out.

[paragraje]

Logging out trouble?

--------------------------------------------------------------------------------

Hi, when i login the username appears on the online users box, when you logout it goes. However if you close the internet browser instead of logging out the username stays and you username will show more than once if you close the internet browser again and again until you press logout. I know why the problem is, it is because when you logout it deletes the username, how can i avoid that problem, any ideas???

You need two things:

1) When you login, you delete any existing login sessions for your name.
2) You create a script that executes on every page that checks for "idle" users. Any user over a specified time (10 minutes for example) is then automatically logged out.

For #2, when someone logs in, you log the date/time in their own "last activity" field. Every page the user accesses, their date/time activity is updated to the current time. Before updating the date/time activity field for the user, however, you check ALL USERS' date/time activity fields to see if their last activity is more than 10 minutes behind the current date/time. If it's been more than 10 minutes from the current time, you log them out.

[andrewK]

The deal is that this is not a rakeback.com issue but a vBulletin issue. vBulletin does exactly what you where describing, but the reason your username shows up more than once if you close and reopen the browser is because the a session gets started but the old one has yet to expire.

Sessions don't expire on the server when you close the browser, the server doesn't know that you closed the browser, how could it? So the session sits idly on the server getting no data and after 30 minutes it just considers it closed and drops it if there is no activity (which there can't be if you close your browser). When you restart the browser it can't use the last session because the browser has lost that information so it starts a new one and vBulletin doesn't check if there are any duplicate sessions for the same username going on (which, in this case, there now are) because it is legal to have more than 1 session for the same username going on. This is why that shows up.

This is not really a bug, nor is it a bug that we have a lot of control over, its vBulletin and its acting normally.