| Summary | last_login pref not updated with file cache enabled |
| Queue | Horde Groupware |
| Queue Version | 1.0-RC3 |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | pascal (at) vmfacility (dot) fr |
| Created | 12/01/2006 (6827 days ago) |
| Due | |
| Updated | 12/08/2006 (6820 days ago) |
| Assigned | |
| Resolved | 12/08/2006 (6820 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
bug #2838.stored in ldap I dont see the last_login beeing updated...
by a last_login already initialised.
So i still don't exactly know how to trigger this last_login pref not
beeing updated. Very annoying...
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ last_login pref not updated with file cache enabled
Queue ⇒ Horde Groupware
for this appl in bug manager).
I am using a composite driver with ldap and cyrus as auth backends.
I have noticed that last_login, and possibly other kind of prefs, is
not updated in the hordePerson ldap attribute when I have the caching
system enabled.
I checked in the Auth code that getAuth() is called upon login into
horde and so I guess last_login pref is updated in the session, but it
is not saved on the ldap backend.
All other prefs accessible from the applications and horde options are
saved and restored OK. It seems to me that all session preferences
that are set internally by horde are not saved. I did not find why
while looking at the code but I saw that pref can be cached and depend
on a dirty bit to be effectively saved in the backend. So I disabled
the horde cache and now my last login is saved and restored.
So i might be a bug related to cache behaviour. I used the filesystem
cache driver:
$conf['cache']['default_lifetime'] = 1800;
$conf['cache']['params']['dir'] = Horde::getTempDir();
$conf['cache']['params']['gc'] = 86400;
$conf['cache']['driver'] = 'file';