Fixed in CVS. Thanks for the comparison point!

A related problem seems to be that preferences are not saved (with a 
MySQL backend).



Reverting to an older Prefs cures this.

The current version I am running is a CVS checkout from 04/11/06.



After replacing framework modules, one at a time, I have determined 
that the problem is in "Prefs".  I am not positive on a date of the 
working version, I think it was around 03/26/06.  I do have a copy 
that is working correctly and I have attached it.  I think the option 
got broken sometime shortly after that.



If I install all of the framework from 04/11/06 and then replace only 
Prefs with the older version, the fullname hook option works with the 
fullname pref is locked.

What Horde version are you using? And do you remember what the working 
version was, or if it was a CVS checkout, the date and branch?

Setting a hook for fullname and locking the fullname pref cause the 
hook not to be executed.  For the hook to be executed, the fullname 
pref must not be locked.



uncomment _prefs_hook_fullname (gecos) from hooks.php



Set prefs.php - fullname to be "locked" with no value

$_prefs['fullname'] = array(

     'value' => '',

     'locked' => true,

     'hook' => true,

     'shared' => true,

     'type' => 'text',

     'desc' => _("Your full name:")

);



After login and composing a new message the fullname is not displayed. 
  Changing the locked to false and nothing else will work.



According prefs comment:

// user full name for From: line

// If you lock this preference, you must specify a value or a hook for it in

// horde/config/hooks.php.



Removing the value line in the prefs.php has no effect on the problem. 
  Since a hook is specified, this should work.  This option worked 
correctly as listed a few months ago.  Using an older revision of 
Horde framework makes this work.