Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
This is mainly a bugfix release, ensuring better Drupal 11 support and fixing some followup bugs from the previous releases.
The 2.0.x and 8.x-1.x versions are the same. Most users should upgrade to the 2.x version. Only users that have a downstream dependency on autologout 8.x-1.x should use the older release.
This is mainly a bugfix release, ensuring better Drupal 11 support and fixing some followup bugs from the previous releases.
The 2.0.x and 8.x-1.x versions are the same. Most users should upgrade to the 2.x version. Only users that have a downstream dependency on autologout 8.x-1.x should use the older release.
Fix for a TypeError in Drupal\autologout\AutologoutManager::construct() which triggers a fatal error when using redirect_404 module (sub module of redirect).
First beta release of the module. The module is tested and working as expected. Warning: This release is not yet ready for production. More testing is necessary.
This is the upgraded version of the 6.x-4.x branch, it includes all the old features as well as some new features. Such as configurable timeout times based on Role/User. This new version is for drupal 7.x
This is more or less a complete rewrite of this module. After a given timeout has passed, users are given a configurable session expired prompt. They can reset the timeout, logout, or ignore it in which case they'll be logged out after a the padding time has elapsed. This is all backed up by a server side logout if js is disable or bypassed. Initial development of the 6.x-4.x branch, and this release, is sponsored by Intel.
Description
===========
This is more or less a complete rewrite of this module. After a given timeout has passed, users are given a configurable session expired prompt. They can reset the timeout, logout, or ignore it in which case they'll be logged out after a the padding time has elapsed. This is all backed up by a server side logout if js is disable or bypassed.
This now includes all the new features from the 7.x.4.x branch. Marked by a bold asterisk.
One Session allows the Administrator to define by role which users can have multiple sessions at a time.
If One Session is enforced the User is restricted to one session. If a restricted user logs on the sessions table is checked, if the users is found to have other sessions: those sessions are set inactive, the user is notified and the event is written to the log.
If a user is in a restricted role and a role that is unrestricted, the One Session feature has no effect.