Autologout - How not to terminate user session when they are editing entry
| Project: | Automated Logout |
| Version: | 6.x-1.5 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I am still quite new to Drupal and offer my apologies for the duplicate post. I previously posted my question http://drupal.org/node/250492 and it was suggested that I post it here.
The Automated Logout module (Autologout v1.5) has the following text in the documentation file. Can someone explain this in a more simple way? I am not clear where to find the "Browser refresh delta" or the "meta refresh" settings, and have encountered a user who has already been stung by being logged out while editing their blog. Does this mean we have to extend the timeout value for all activities or is there another setting to save those who are editing content?
Thanks,
Izzy
Browser refresh delta:
If this is set to a non zero value, this time will be added to the
"Timeout value in seconds" variable and be used to set a :-
line in the section of the page. It's likely that clocks
won't be perfect so make the browser wait sometime longer than the
actual time out value. This effectively sends the browser back to
the homepage with the user logged out. Set this to 0 (zero) to disable
the tag.
Note, as stated above, we test for content submission before doing
a logout so that users do not loose work. However, if you force a
meta refresh, this is not possible as the browser will refresh the
page without doing a submit or a preview. In this case, users may
loose work so use this option carefully. There's nothing more
annoying than loosing your work (except maybe hemorrhoids! ;)
#1
To summarize, yes if users are editing content and the automated logout triggers their changes will not be saved.
For people who use Automated logout to increase the security of their site by having the server log people out, this is a good thing. Also, the meta refresh isn't actually doing the logout. Even if you set the refresh to 0, the server will expire the user session and the content being edited won't be saved.
How would you like to use the logout module? Perhaps you have a new use case we need to consider, and we can change this into a feature request.
#2
Is it possible to identify when a user enters create, edit, or reply mode. If so, could the module either add some additional time or set a flag to not terminate the session. When the user exits those modes with a save or cancel the flag could be removed.
Is this thinking too simplistic, wishful thinking maybe?
Izzy
#3
house cleaning.