[Tickets #1236] Cannot access Free/Busy data on a Kolab backend

[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=1236
-----------------------------------------------------------------------
 Ticket     | 1236
 Updated By | a.gungl at gmx.de
 Summary    | Cannot access Free/Busy data on a Kolab backend
 Queue      | Kronolith
 Version    | HEAD
 State      | Assigned
 Priority   | 1. Low
 Type       | Bug
 Owners     | Stuart K Bingë
-----------------------------------------------------------------------


a.gungl at gmx.de (2005-02-10 05:56) wrote:

Okay, here is a workaround which doesn't touch the core Horde
implementation. The idea is to fool the error handling which prevents using
the storage driver to retrieve an URL. So we map an existing Kolab LDAP
field to freebusyUrl. Horde won't find f/b data under the URL, but at least
the URL is valid. So we continue with the processing towards the storage
driver which will finally provide the f/b data.
It would be good if Kolab could provide the URL in LDAP, but this is another
story.

The file to be changed is turba/config/sources.php.dist

--- sources.php.dist.orig       2005-02-10 14:52:47.128198440 +0100
+++ sources.php.dist    2005-02-10 14:54:52.272173664 +0100
@@ -566,6 +566,7 @@
             'cellPhone'         => 'mobile',
             'fax'               => 'fax',
             'notes'             => 'description',
+            'freebusyUrl'       => 'kolabHomeServer',
         ),
         'search' => array(
             'name',

Please apply the change to CVS.