| Summary | fix _buildSearchQuery() to generate correct search filter |
| Queue | Turba |
| Queue Version | Git master |
| Type | Bug |
| State | Duplicate |
| Priority | 3. High |
| Owners | |
| Requester | Joerg.Pulz (at) frm2 (dot) tum (dot) de |
| Created | 06/04/2013 (4391 days ago) |
| Due | |
| Updated | 06/04/2013 (4391 days ago) |
| Assigned | |
| Resolved | 06/04/2013 (4391 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | Yes |
State ⇒ Duplicate
Bug #12297New Attachment: turba_ldapfilter_fix[1].diff
Here is the correct one.
Priority ⇒ 3. High
New Attachment: turba_ldapfilter_fix.diff
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ fix _buildSearchQuery() to generate correct search filter
Type ⇒ Bug
State ⇒ Unconfirmed
contact or when Kronolith asks for the freebusyUrl.
The generated search filter for an manually contact search looks like:
(|)(mail=*<searchstring>*)(telephonenumber=*<searchstring>*)
but should look like:
(cn=*<searchstring>*)(mail=*<searchstring>*)(telephonenumber=*<searchstring>*)
The generated search filter for Kronolith automated freebusyUrl search
looks like:
(|)
but should look like:
(mail=user@domain.tld)
The attached patch fixes this. I don't know why "$key == 'OR'" causes
this error as the value of $key is "0" when this occurs.