| Summary | ldap driver not searching for correct ingo boundar |
| Queue | Ingo |
| Queue Version | 1.1.2 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | tansy (at) pacific (dot) net (dot) sg |
| Created | 12/14/2006 (6838 days ago) |
| Due | 10/31/2006 (6882 days ago) |
| Updated | 12/21/2006 (6831 days ago) |
| Assigned | |
| Resolved | 12/21/2006 (6831 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Due ⇒ 10/31/2006
wasn't updated. Fixed now - thanks.
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ ldap driver not searching for correct ingo boundar
Due ⇒ 11/30/2006
Queue ⇒ Ingo
Not sure if I am doing something wrong, but it seems that ldap.php is
not detecting the Ingo filter boundaries correctly.
In ingo/lib/Driver/ldap.php, there are two lines:
if (strpos($value, "##INGO\n") !== false) {
However, on examination of the filtering scripts generated by Ingo,
and the screen captures on http://www.horde.org/ingo/screenshots/, it
seems that there is no such line: ##INGO.
This causes the "Deactivate Script" and "Show Active Script" buttons
in Ingo to fail.
The strpos() line should be searching for lines like "# maildrop
script" (depending on the filter used) instead?