First, thanks very much for this module. It has been very useful in it's earlier 6.x-2.x version and we have been using the 6.x-4.x version since the beginning of December.
I think this is a bug not just a support question or a feature request, but I stand to be corrected.
I am using autologout with multiple tabs in FF 3.6.x open to the same site. Autologout is timing out on one of the tabs even while another tab for the same site is in active use. Furthermore, the warning is not displayed in the currently active tab so the user cannot be aware to reset it and the user is not aware when the logout occurs.
This is particularly troublesome if the user is adding or editing content because it is not until they go to save that problems occur. Sometimes there is a significant delay after pressing "save" and eventually the user gets the "access denied" message and their work is lost.
Please correct me if this a support or feature request. Any suggestions would be appreciated.
Thanks,
Izzy
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | autologout-multi_tabs-1024508-1024508.patch | 5.24 KB | johnennew |
| #12 | autologout-multi_tabs-1024508-1024508.patch | 5.41 KB | johnennew |
| #10 | multiple-tabs-1024508-10.patch | 4.33 KB | kevin.dutra |
| #9 | mulitple-tabs-1024508-9.patch | 3.82 KB | kevin.dutra |
| #8 | mulitple-tabs-1024508-8.patch | 2.97 KB | kevin.dutra |
Comments
Comment #1
Equinger commentedSame here. Subscribing.
Comment #2
Equinger commentedAny thoughts on this? I would love to help on this. I just need some thoughts about what could be going on.
Comment #3
izmeez commentedSorry, don't know what to suggest. We went back to 6.x-2.x version.
Comment #4
Equinger commentedIf this was changed to a simple alert, wouldn't the proper tab reopen? It's not the best solution, but it would be better than the current situation.
Comment #5
yogeshchaugule8 commentedSubscribing
Comment #6
dppeak commentedAny update on this?
Comment #7
enboig commentedI think and ajax could check for 'access' in {users} before logging out. Then decide if checout is necessary or an update to timer is necessary.
Comment #8
kevin.dutra commentedIt's been a while, so hopefully some of you guys are still following this thread :)
Attached is a possible solution for this problem. Along the lines of what enboig proposed, an AJAX call gets spun off when the timeout occurs. If there is additional time left (i.e. the user is off in another tab/window navigating around), then the timer is reset to the amount left, so all the tabs/windows open for that session should close at the same time. (Well, almost...there's going to be a little bit of difference accounting for the time it takes the response to get back.)
Don't forget to clear your menu cache to pick up the new item.
Comment #9
kevin.dutra commentedActually this patch is a bit better--you would have needed to click the reset button on each tab/window before to prevent yourself from being logged out.
Comment #10
kevin.dutra commentedUpdating my patch in #9 to fix a problem revolving around AJAX requests. When they return, they'll trigger an additional timeout to be set, which will end up giving you multiple dialogs when the timeouts start expiring. This is noticeable on something like a Views page that has AJAX enabled.
Comment #11
joekersThanks Kevin, I managed to use this patch and modify it for the Drupal 7 version of the module.
Comment #12
johnennew commentedThe patch is 10 worked for me with some modification for Drupal 7. Please find a re-roll for 7.x-4.x branch attached.
Comment #13
johnennew commentedSorry, left some debug in there. Here is another patch for 7.x-4.x
Comment #14
johnennew commentedI have applied the patch in #13 to the 7.x-4.x branch.
Resetting to 6.x-4.x so it can be backported.
Comment #15
johnennew commentedHi @kevin.dutra
I committed your patch in #10 to the 6.x-4.x branch.
Rgds