+1

I agree with Jan.  If you can't change a preference, it doesn't make 
any sense to show the value.  That's just confusing.

A locked preference is no different than some feature/UI element that 
can't be changed because a pref doesn't even exist for it.

Well, I can agree just in parts; we encounter often questions by our 
customers complaining about settings they can not see and where they 
don't know what the default settings are..
So sometimes our helpdesk is asking the customer to navigate to the 
settings-page and to read out some values they see.

A simple example would be:
"Are my attachment saved on outgoing messages?"
"In which folder are my attachments saved?"
"How often do you clean the SPAM-folder?"
"Are my external mail-accounts configured? And which one?"

So, you know, there arise some questions the clients could read by themselves.

I must admit, I don't really know if it would be a big change in code 
or if it is enough modular to enter some new functions "on the fly"..

IMO this would be more confusing to the user, to see options he cannot 
even change. The simpler the better.

Hi guys,
I would like to question if it would be possible to add a new "global 
$_prefs" variable in Horde so it would be available for all..

Let me explain what I mean:

Since every service provider would like to lock down some settings the 
user should never touch, like for example the "$_prefs['id']", 
"$_prefs['fullname']", "$_prefs['from_addr']", you have inserted the 
"lock" feature in horde which is doing a good job!

The definition about locking is: "Do not show this preference in the 
UI and don't allow changing by any mechanism."

Wouldn't it be nice to have some "lock" which *shows* the preference 
*without* writing a hook? Maybe the value could be grayed out so the 
user can't change it, but can see what value has been set by the admin?

Thank you!