Jan Schneider horde.org> writes:
> The search_fields preference expects a json-encoded array. Just pass
> $out through json_encode().
>
> Jan.
I already encoded it, my hook is:
public function prefs_init($pref, $value, $username, $scope_ob)
{
switch ($pref) {
case 'a
Marco csi.it> writes:
> (but in web preferences address book have still have only "name" and "email"
> selected, ...I'm confused)
...this is beacuse in backend I have:
table: horde_prefs
pref_scope: horde
pref_name: search_fields
pref_value:
7724a026e66eb49c8bc20f75bc5dcf56
d05a78fe4ca320316306
Jan Schneider horde.org> writes:
> > Upgrading from horde 3 I also see that there are other preferences
> > not read from
> > db: 'fullname' and all about multiple identities.
>
> fullname is an identity pref, it's not used or read from the backend
> individually.
> I'm not sure what mean wi
> It seems they are not read from backend. I make this example to be more
> clear.
>
> A user have multiple identities as defined in the backend:
>
I have a hook writing three identities and imp reads them and uses them. The
identity details don't show up in imp's separate configuration fields
Ralf Lang b1-systems.de> writes:
> I have a hook writing three identities and imp reads them and uses them. The
> identity details don't show up in imp's separate configuration fields though.
In my prefs I only locked 'from_addr'. All identities work on
horde-webmail-1.2.9: IMP uses them and
