<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>last_login pref not updated with file cache enabled</title>
  <pubDate>Wed, 15 Oct 2008 23:14:40 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/4724</link>
  <atom:link rel="self" type="application/rss+xml" title="last_login pref not updated with file cache enabled" href="http://bugs.horde.org/ticket/4724/rss" />
  <description>last_login pref not updated with file cache enabled</description>

  
  
  <item>
   <title>I am using horde groupware webmail edition rc1 (no queue is </title>
   <description>I am using horde groupware webmail edition rc1 (no queue is defined 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';
</description>
   <pubDate>Fri, 01 Dec 2006 08:59:59 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/4724#t26968</link>
  </item>
  <item>
   <title>well it does not seem linked to the cache system used. I was</title>
   <description>well it does not seem linked to the cache system used. I was tricked 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...</description>
   <pubDate>Fri, 01 Dec 2006 12:24:05 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/4724#t26969</link>
  </item>
  <item>
   <title>I tested an old non composite config - same problem when pre</title>
   <description>I tested an old non composite config - same problem when pref are stored in ldap  I dont see the last_login beeing updated...</description>
   <pubDate>Fri, 01 Dec 2006 12:35:30 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/4724#t26970</link>
  </item>
  <item>
   <title>Duplicate of bug #2838.</title>
   <description>Duplicate of bug #2838.</description>
   <pubDate>Fri, 08 Dec 2006 12:57:54 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/4724#t27215</link>
  </item>
  

 </channel>
</rss>
