| Summary | Support for multiple results retrieving FB info |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | chuck (at) horde (dot) org |
| Requester | almarin (at) um (dot) es |
| Created | 04/22/2008 (6295 days ago) |
| Due | |
| Updated | 04/24/2008 (6293 days ago) |
| Assigned | |
| Resolved | 04/24/2008 (6293 days ago) |
| Milestone | |
| Patch | No |
Assigned to Chuck Hagenbuch
State ⇒ Resolved
Kronolith 2.2 RC. Thanks!
Priority ⇒ 1. Low
New Attachment: FreeBusy.php.patch
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Support for multiple results retrieving FB info
Type ⇒ Enhancement
State ⇒ New
is LDAP), and sometimes, an user with a freebusyurl could be in both
of them with a duplicate freebusyurl entry.
In that cases, kronolith gives me an error (freebusy info not found).
It happens because kronolith uses turba's api method 'getField'. This
method, if parameter $multiple=true not defined, returns an
PEAR_Error: More than 1 entry found.
So... I wonder... Should be desirable that, at least, the first result
was returned instead an PEAR_Error?
To give a pointer, I attach a simple patch to support this behaviour