[horde] change in horde 2.2.6 breaks imp identity locking ?

[Jan Schneider]

Zitat von Adam Arrowood <adam.arrowood at oit.gatech.edu>:

> (posting this to the horde and imp lists, because the change was in 
> horde, but
> effects imp...)
>
> In horde 2.2.6, the following lines were added to /horde/config/prefs.php:
>
>> // Identity preferences.
>>
>> // default identity
>> // Don't change anything here.
>> $_prefs['default_identity'] = array(
>>     'value' => 0,
>>     'locked' => false,
>>     'shared' => true,
>>     'type' => 'implicit'
>> );
>>
>> // identities array
>> // Don't change anything here.
>> $_prefs['identities'] = array(
>>     'value' => 'a:0:{}',
>>     'locked' => false,
>>     'shared' => true,
>>     'type' => 'implicit'
>> );
>
> which, in my case, seems to break identity locking in imp, via
> /horde/imp/config/prefs.php:

Yes, you need to lock the identities in both files.

>> // default identity
>> // Set locked to true if you don't want the users to have multiple 
>> identities.
>> $_prefs['default_identity'] = array(
>>     'value' => 0,
>>     'locked' => true,
>>     'shared' => true,
>>     'type' => 'implicit'
>> );
>
> I don't want users to have multiple identities. With the new lines, users are
> able to create new identities, despite my settings in the imp prefs 
> file. If I
> comment out the new lines in the horde prefs file, then identity 
> locking seems
> to work again. What do I fixes/new features do I lose by commenting 
> them out ?

The users' full names are not available in the portal view after logging in.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/