[Tickets #6822] Re: Hooked prefs won't get stored

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6822
-----------------------------------------------------------------------
 Ticket             | 6822
 Updated By         | manuel at mausz.at
 Summary            | Hooked prefs won't get stored
 Queue              | Horde Framework Packages
 Version            | FRAMEWORK_3
 Type               | Bug
 State              | Feedback
 Priority           | 2. Medium
 Milestone          |
 Patch              |
 Owners             |
-----------------------------------------------------------------------


manuel at mausz.at (2008-06-03 04:14) wrote:

> Why isn't this the right behavior?

#1 It's not documented that way (from hooks.php)
 * NOTE 3: Any preference that is NOT LOCKED, that is set by a hook, WILL
BE
 * SAVED WITH THAT VALUE. This means several things:
 * 1) Users will get the results of the hook set for them in their
 *    preferences.
 * 2) By virtue of this, the next time they log in and load their
 *    preferences, the hook will NOT be called, because in their last
session,
 *    we saved the results of the hook for them. However, if the
preference is
 *    locked, the result of the hook will never be saved.

#2 We're hooking a lot of preferences for initial setup. If they won't be
stored any more, this will generate a bunch of unnecessary SQL querys.

#3 Why should unlocked prefs not get stored? (counter question)