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

List:       horde-bugs
Subject:    [Tickets #1236] Cannot access Free/Busy data on a Kolab backend
From:       bugs () coyote ! horde ! org
Date:       2005-01-29 19:46:24
Message-ID: 20050129194624.1ADA634E55 () coyote ! horde ! org
[Download RAW message or body]

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

Ticket URL: http://bugs.horde.org/ticket/?id=1236
-----------------------------------------------------------------------
 Ticket     | 1236
 Updated By | a.gungl@gmx.de
 Summary    | Cannot access Free/Busy data on a Kolab backend
 Queue      | Kronolith
 Version    | HEAD
 State      | Feedback
 Priority   | 1. Low
 Type       | Bug
 Owners     | Stuart K Bingė
-----------------------------------------------------------------------


a.gungl@gmx.de (2005-01-29 11:46) wrote:

After another session I've pinned down the problem as follows:

The critical section in the code is in kronolith/lib/Kronolith.php in the
lines 843-858. There is an attempt to get the f/b URL from an addressbook,
which doesn't seem to work with a Kolab backend. My understanding of the
code is, Horde should just continue and use the storage driver to get the
f/b data. That implementation is correct for a Kolab backend. However, I
didn't get the code in the storage driver executed. Once I commented out the
lines 843-858, I could read f/b data from the Kolab server and everything
else worked as expected.

I hope this analysis is of help for fixing the real problem which seems to
be behind the mentioned lines of code. Commenting it out won't be an option
for Horde on another backend. ;-)



-- 
You are subscribed to this list as: horde-bugs@progressive-comp.com
To unsubscribe, mail: bugs-unsubscribe@lists.horde.org
[prev in list] [next in list] [prev in thread] [next in thread]