[Tickets #2829] NEW: last_login preference not stored

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2829
-----------------------------------------------------------------------
 Ticket             | 2829
 Created By         | heinz at htl-steyr.ac.at
 Summary            | last_login preference not stored
 Queue              | Horde Framework Packages
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


heinz at htl-steyr.ac.at (2005-10-22 04:14) wrote:

Background:
I'm using the Horde-Framwork with imp-Authentification.
The preferencies backend is LDAP.

When I'm including ingo in imp then the last_login preference is not
stored!

Reason:
- The imp-preferencies are loaded (old value for last_login is retrieved)
- Auth.php sets the new value for last_login
- Then the ingo-preferencies are loaded and overwrite the new value for
last_login

Resolution:
Store the new "dirty-value" for last_login after setting it:

Code snippet:
     // Set the user's last_login information.
     $last_login = array('time' => time(),
                                   'host' =>
@gethostbyaddr($_SERVER['REMOTE_ADDR']));
     $GLOBALS['prefs']->setValue('last_login', serialize($last_login));
     //NEW: ************************Store it ! *********************
     $GLOBALS['prefs']->store();