[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kronolith
Subject:    Re: [kronolith]
From:       Chuck Hagenbuch <chuck () horde ! org>
Date:       2008-04-22 15:46:27
Message-ID: 20080422114627.13075pb9ceak5v48 () technest ! org
[Download RAW message or body]

Quoting Alfonso Marí­n Marí­n <almarin@um.es>:

> 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 behavior

Makes sense to me - can you please create a ticket on  
http://bugs.horde.org/ and attach your patch?

Thanks,
-chuck

-- 
"I have concerns that we are not behaving like a mature, responsible,  
collection of interdependent organisms." - Rick O.
-- 
Kronolith mailing list - Join the hunt: http://horde.org/bounties/#kronolith
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: kronolith-unsubscribe@lists.horde.org

[prev in list] [next in list] [prev in thread] [next in thread]