[Tickets #13945] Re: Autocomplete with custom parameter not working for LDAP

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13945
------------------------------------------------------------------------------
  Ticket             | 13945
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Autocomplete with custom parameter not working for LDAP
  Queue              | Turba
  Version            | 4.2.5
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2016-07-21 19:00) wrote:

>> Ticket: 10913
>
> I don't think, it is duplicate of 10913.  My concern is with  
> searching attribute and not return attribute.  can this bug be  
> re-opened.

This actually is (mostly) a duplicate of Ticket: 10913. The field is  
being correctly searched (when the field is properly included in the  
search_fields pref). The issue is that we have code in Turba that  
filters out results in certain cases in order to prevent duplicate  
hits. E.g., if the contact has two email addresses, only the one with  
the matching text is returned.