Hi,
I've got some questions concerning the new extended addressbook:
- uid as RDN
My LDAP setup requires uid as RDN. Therefore I added
'LDAP_rdn' => 'uid',
'required_fields' => array("mail", "cn", "sn", "uid"),
'search_fields' => array('mail', 'cn', 'sn', 'givenName','uid'),
to the configuration. How can I make this field visible in the user interface?
My current workaround is
'organization' => 'uid'
But this is not very intuitive. Especially since this field is not automatically visible when adding a new contact.
Also adding addresses from E-Mails does not work this way.
- Work adress
How can I have two sets of address fields (home and work address) like with the personal addressbook (SQL)?
I tried it with
'street:main' => 'street',
'zipcode:main' => 'postalCode',
'locality:main' => 'l',
'region:main' => 'st',
'country:main' => 'co',
'street:work' => 'workStreet',
'zipcode:work' => 'workPostalCode',
'locality:work' => 'workLocalityName',
'region:work' => 'workStateOrProvinceName',
'country:work' => 'workFriendlyCountryName',
but I get only the first set as home address and can't add another address block.
Thanks, Manfred
List info: http://lists.roundcube.net/dev/ BT/aba52c80
Manfred Usselmann wrote:
Hi,
Hi Manfred,
I've got some questions concerning the new extended addressbook:
- uid as RDN
My LDAP setup requires uid as RDN. Therefore I added
'LDAP_rdn' => 'uid', 'required_fields' => array("mail", "cn", "sn", "uid"), 'search_fields' => array('mail', 'cn', 'sn', 'givenName','uid'),to the configuration. How can I make this field visible in the user interface?
Currently you can map LDAP attributes only to a list of predefined and hard-coded fields of the Roundcube address book. And as you correctly figured out, there's no field like "UID" available so far. This is certainly something we have to improve but for now you have to live with your workaround. Of course we also accept patches to the Roundcube code that would improve this ;-)
Also adding addresses from E-Mails does not work this way.
Outch, right. When adding addresses from emails, only name and email address data is present. How should a UID be automatically derived from these? Adding nevertheless works in most setups where the email address is used for RDN.
- Work adress
How can I have two sets of address fields (home and work address) like with the personal addressbook (SQL)?
I tried it with
'street:main' => 'street', 'zipcode:main' => 'postalCode', 'locality:main' => 'l', 'region:main' => 'st', 'country:main' => 'co', 'street:work' => 'workStreet', 'zipcode:work' => 'workPostalCode', 'locality:work' => 'workLocalityName', 'region:work' => 'workStateOrProvinceName', 'country:work' => 'workFriendlyCountryName',but I get only the first set as home address and can't add another address block.
I just committed some changes to SVN trunk (r5377) which should fix this. However, you should use *:work instead of *:main to have the subtypes labelled correctly.
Regards, Thomas _______________________________________________ List info: http://lists.roundcube.net/dev/ BT/aba52c80
Hi Thomas,
Am 30.10.2011 17:05, schrieb Thomas Bruederli:
Thanks a lot for your reply.
Manfred Usselmann wrote:
I've got some questions concerning the new extended addressbook:
- uid as RDN
My LDAP setup requires uid as RDN. Therefore I added
'LDAP_rdn' => 'uid', 'required_fields' => array("mail", "cn", "sn", "uid"), 'search_fields' => array('mail', 'cn', 'sn','givenName','uid'),
to the configuration. How can I make this field visible in the user interface?
Currently you can map LDAP attributes only to a list of predefined and hard-coded fields of the Roundcube address book. And as you correctly figured out, there's no field like "UID" available so far. This is certainly something we have to improve but for now you have to live with your workaround.
OK.
Of course we also accept patches to the Roundcube code that would improve this ;-)
I would love to help but unfortunately I'm already overloaded.
Also adding addresses from E-Mails does not work this way.
Outch, right. When adding addresses from emails, only name and email address data is present. How should a UID be automatically derived from these?
The most sensible thing IMO would be to fill the UID with the email address in this case. Or maybe generate a unique number with function uniqid or similiar.
Adding nevertheless works in most setups where the email address is used for RDN.
- Work adress
How can I have two sets of address fields (home and work address) like with the personal addressbook (SQL)?
I tried it with
'street:main' => 'street', 'zipcode:main' => 'postalCode', 'locality:main' => 'l', 'region:main' => 'st', 'country:main' => 'co', 'street:work' => 'workStreet', 'zipcode:work' => 'workPostalCode', 'locality:work' => 'workLocalityName', 'region:work' => 'workStateOrProvinceName', 'country:work' => 'workFriendlyCountryName',but I get only the first set as home address and can't add another address block.
I just committed some changes to SVN trunk (r5377) which should fix this. However, you should use *:work instead of *:main to have the subtypes labelled correctly.
Thanks, I will try it out.
Regards, Manfred
List info: http://lists.roundcube.net/dev/ BT/aba52c80
-
Manfred Usselmann -
Thomas Bruederli