[Tickets #6263] Problem adding contact groups when using composite fields (LDAP)

bugs at horde.org bugs at horde.org
Thu Feb 14 22:22:47 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=6263
-----------------------------------------------------------------------
 Ticket             | 6263
 Created By         | dirk at liji.de
 Summary            | Problem adding contact groups when using composite fields (LDAP)
 Queue              | Turba
 Version            | 2.2-RC2
 Type               | Bug
 State              | Unconfirmed
 Priority           | 1. Low
 Milestone          | 
 Patch              | 
 Owners             | 
-----------------------------------------------------------------------


dirk at liji.de (2008-02-14 17:22) wrote:

When using composite fields (e.g. in LDAP) in some configurations it's
impossible to add contact groups to the same address book.
I use a composite field similar to the example given in sources.php.
        'name' => array(
            'fields' => array('lastname', 'firstname'),
            'format' => '%s, %s',
            'attribute' => 'cn'),
Since the 'name' attribute, which will be mapped to 'cn' (cn as contact
name occured to me to be most logic choice since sn=surname and
givenName=first name are already ldap attributes) is a composite field, the
name cannot be specified when creating a contact group so cn stays empty
and the ldap server rejects the new object.

Is it possible to add something like a fallback attribute, in case the
composite field is empty/invalid (or rejected by the backend), another
field can be used as 'second try', so name could be the fallback field in
my case.




More information about the bugs mailing list