| Summary | Using "emails" instead of "email" atribute in backend map configuration for ldap server breaks auto complete of addresses |
| Queue | Turba |
| Queue Version | 3.0.12 |
| Type | Bug |
| State | Duplicate |
| Priority | 3. High |
| Owners | |
| Requester | mehmet (at) giritli (dot) eu |
| Created | 03/28/2012 (4824 days ago) |
| Due | |
| Updated | 03/29/2012 (4823 days ago) |
| Assigned | |
| Resolved | 03/29/2012 (4823 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Using "emails" instead of "email" atribute in backend map configuration for ldap server breaks auto complete of addresses
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
to find the bug!
As you know, it is quite common to have multiple emails for a ldap
contact. I am used to handle this by using a map in backends like this:
'map' => array(
'__key' => 'dn',
'__uid' => 'uid',
'name' => 'cn',
'firstname' => 'givenName',
'lastname' => 'sn',
'emails' => 'mail',
.....
This partially solved (except editing:
http://bugs.horde.org/ticket/9554) the problem of using multiple
email addresses per contact with ldap backends. But now with H4 if I
use this kind of map, I do not have auto complete of addresses in the
new mail composition window anymore. Changing "emails" to "email "
brings back auto complete. But obviously I loose the ability to have
multiple emails per contact....
I don't know if anything else has stopped working because of this in H4.