I am using Drupal 4.6.3 in a corporate environment, and users usually don't log off when they leave work, they just close their browser.
Next day their are autotamically logged on, so the last access column at administrate/users (changed column in users table) is not updated at all, it reflects the user's last log in time (or the user's last account edit time).
Since the inactive_user module's reference is the changed column, it will raise warning emails about fake inactivities, since users do use the site, however the module thinks they don't use it.
I'm not sure if this should be categorized as a bug for this module, maybe this is a user and ldap_integration bug for not updating the changed column when users launch their browser, but the bottom line is that the inactive_user module is not working properly.
I also thought about making a patch that would take the user's last timestamp from the accesslog table, however last access statistics might be turned off, and they definitely log last access for only a limited time, so the information from this table would not help in all circumstances.
Comments
Comment #1
andykemp commentedI am having the same problem... Does anyone have a solution??
Comment #2
DriesK commentedHi,
I'm the new mainainer of this module. I ported it to Drupal 4.7 (download available as of today).
In Drupal 4.7, the 'changed' column has been renamed to 'access', and is now updated upon each page request. The time frames used by inactive_user.module therefore correctly reflect user inactivity now. No need anymore to make statistics module a required module for inactive user.
Comment #3
(not verified) commented