[Tickets #2838] Re: LDAP prefs driver overwrites modified Horde prefs in some cases

[bugs@bugs.horde.org]

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

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2838
-----------------------------------------------------------------------
 Ticket             | 2838
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
-Summary            | hordes last_login preference not stored 
+Summary            | LDAP prefs driver overwrites modified Horde prefs in some cases
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
 State              | Assigned
 Priority           | 2. Medium
 Owners             | Chuck Hagenbuch, Horde Developers
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2006-11-22 12:11) wrote:

Merging in some comments for clarity:

"I use ldap backend for preferences.
In horde+imp last_login works.
In horde+imp+ingo last_login does not work anymore.

When imp loads preferences, it load horde preferences as well.
In that step it set last_login with the ldap value,
"display" last_login value
and set last_login to current time.

When ingo loads preferences, it load horde preferences as well.
In that step it set last_login with the ldap value and the
last_login value from imp is lost."

"I think this is actually a general flaw in the Prefs code, in that it
will load Horde preferences regardless of whether they're already loaded.
This is a waste and also, as you diagnosed, can result in overwriting
unwritten values.

I'm still puzzling out the best fix; your way does work, but I think we'll
arrive at something a bit different eventually. Needs to be fixed for at
least the SQL driver as well, possibly more."