[#6638] Support for multiple results retrieving FB info
Summary Support for multiple results retrieving FB info
Queue Kronolith
Queue Version HEAD
Type Enhancement
State Resolved
Priority 1. Low
Owners Chuck Hagenbuch <chuck (at) horde (dot) org>
Requester almarin (at) um (dot) es
Created 04/22/2008 (19 days ago)
Due
Updated 04/23/2008 (18 days ago)
Assigned
Resolved 04/23/2008 (18 days ago)
Attachments FreeBusy.php.patch Download
Milestone
Patch

History
04/23/2008 Chuck Hagenbuch Comment #2
State ⇒ Resolved
Assigned to Chuck Hagenbuch		 Reply to this comment
Looks good - tweaked very slightly and committed. It'll be in the next Kronolith 2.2 RC. Thanks!
04/22/2008 almarin (at) um (dot) es Comment #1
New Attachment: FreeBusy.php.patch Download
Patch ⇒
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Support for multiple results retrieving FB info
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ New		 Reply to this comment
I have configured in turba two different sources (one in BD and other 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