0.4.0

• Unused sessions deleted: session rows unused for longer than a session lives (gc_maxlifetime)
  are deleted, in batches. PHP deletes them only when its own clean-up runs, and many servers switch
  that off (session.gc_probability = 0), so the table only grew — a row for every visit. Done by
  bin/sweep.php (every 5 minutes from cron); without cron, one batch an hour on a page request.
  A working sign-in is never touched.
• Session table on the sessions page: rows, size, the oldest, and the last clean-up.
• Sign out everybody else: one button ends every sign-in but your own current one, kept devices
  too (noted in "Changes to sign-in times").
• Upgrade from 0.3.x: Modules → Active Sessions → Upgrade (no database change).

0.3.2

• A comment in the code rewritten in plain terms. No change in behaviour; no database change.

0.3.1

bin/sweep.php ends every sign-in past its time and forgets old records from cron, so it no longer waits for somebody to open an Omeka page: pages outside Omeka that read the session table (a site's own staff pages) no longer take an expired sign-in for a working one on a quiet day. Run it every 5 minutes as the web server's user (see README). Silent unless it did something; exit 1 on an error. The web sweep is unchanged. Upgrade from 0.3.0: Modules, Active Sessions, Upgrade (no database change). See CHANGELOG.md.

0.3.0

A global admin can give one person their own sign-in time (7 days, 30 days, longer if the server allows, or the longest the server allows) instead of their role's, and keep one device signed in for the longest the server allows; the person's other devices follow the rule. The longest is read as the site runs (the shorter of gc_maxlifetime and cookie_lifetime), so nothing outlives what the server keeps. Sign out on every device for one person; sign-outs end kept sign-ins too; a deactivated person is signed out on their next request. Every change is noted. Nothing set = 0.2 exactly. Upgrade from 0.2.0: Modules, Active Sessions, Upgrade (adds three columns). See CHANGELOG.md.

Active Sessions 0.2.0

A sign-in now ends after a set time by role, kept on the server: everybody 12 hours, the roles you choose (default: global admin) 7 days, both in the module's settings (0 = no limit). A sign-in past its time is ended on the person's next request (the login page says why) and, every few minutes, its session row is deleted, so pages outside Omeka that read the session table see it gone too. Sign-ins from before the upgrade start their clock when first seen, so upgrading signs nobody out at once. The sessions page says the rule at the top and when each sign-in ends. Upgrade from 0.1.0: Modules, Active Sessions, Upgrade (adds one column). See CHANGELOG.md.

Active Sessions 0.1.0

First public release.