[Tickets #1822] Kolab: problem handling events having no time associated

[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=1822
-----------------------------------------------------------------------
 Ticket             | 1822
 Updated By         | a.gungl at gmx.de
 Summary            | Kolab: problem handling events having no time associated
 Queue              | Kronolith
 Version            | HEAD
 State              | Assigned
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Stuart K Bingë
-----------------------------------------------------------------------


a.gungl at gmx.de (2005-04-20 08:12) wrote:

I've tried mktime, but without success: What I have found in the meantime is
the need to fix kronolith/lib/Driver/kolab.php in function saveEvent($event)
around line 180 like this:

        $k->setVal('alarm', $event->getAlarm());
        if ($event->isAllDay()) {
            $k->setVal('start-date',
Kolab::encodeDate($event->start->timestamp()));
            $k->setVal('end-date',
Kolab::encodeDate($event->end->timestamp()));
        } else {
            $k->setVal('start-date',
Kolab::encodeDateTime($event->start->timestamp()));
            $k->setVal('end-date',
Kolab::encodeDateTime($event->end->timestamp()));
        }

        switch ($event->status) {

This is because the Kolab XML format expects date-only values for events
with a duration of a whole day.

However this increases the timezone problem. In function encodeDate($date =
false) in framework/Kolab/kolab.php there I find time values like
2005-04-20T22:00:00Z for GMT+2 midnight, but this is 2005-04-21 (00:00) in
our time. Reducing the values 2005-04-20T22:00:00Z and 2005-04-21T22:00:00Z
to the date gives 2005-04-20 and 2005-04-21 instead of 2005-04-21 two times.
:-(
So I end up with a two day long event instead of one day.