[Tickets #3010] NEW: locked prefs create system defaults regardless of what prefs the user sets
bugs@bugs.horde.org
bugs at bugs.horde.org
Mon Nov 21 12:51:55 PST 2005
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=3010
-----------------------------------------------------------------------
Ticket | 3010
Created By | liamr at umich.edu
Summary | locked prefs create system defaults regardless of what prefs the user sets
Queue | Horde Base
Version | HEAD
State | New
Priority | 1. Low
Type | Enhancement
Owners |
-----------------------------------------------------------------------
liamr at umich.edu (2005-11-21 12:51) wrote:
It would be useful in setting site wide preferences (for all horde apps), if
when a preference was locked, the setting from config/prefs.php took
presidence over any user supplied setting.
As it is now, horde will load the user prefs from the prefs backend, and
prevent them from changing settings if that pref is locked.
I can see situations where sites may have deployed with a preference
enabled, but then wanted to turn it off (maybe temporarily). I realize that
you could lock the pref, and then delete the pref from the pref. backend,
forcing the default value, but that causes problems if you want to unlock it
at a later date w/o loosing the user defined values.
More information about the bugs
mailing list