[Tickets #904] Ingo Screwed Up

[bugs at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=904
-----------------------------------------------------------------------
 Ticket     | 904
 Updated By | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary    | Ingo Screwed Up
 Queue      | Ingo
 Version    | 1.0-RC2
 State      | Assigned
 Priority   | 2. Medium
 Type       | Bug
 Owners     | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2004-12-05 23:19) wrote:

BTW - your diagnosis of the problem on 11/30 is incorrect. A call to
$ingo_storage->retrieve(INGO_STORAGE_ACTION_FILTERS) won't return the
details of the blacklist/whitelist (since, as you have correctly noted,
those details exist in separate preferences) but it will return the
blacklist and whitelist placeholder entries - these are needed to indicate
where the black/whitelist entry exists in the filter list, whether it is
disabled or not, etc.

So if the blacklist/whitelist placeholder entry is not showing up in the
return from the retrieve() call it is either because the backend doesn't
support it (but sieve does so that's not the problem) or it is because some
other app is handling the blacklist/whitelist API calls.  See
ingo/lib/Script.php:167-176