[Tickets #1822] NEW: 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
 Created By         | a.gungl at gmx.de
 Summary            | Kolab: problem handling events having no time associated
 Queue              | Kronolith
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


a.gungl at gmx.de (2005-04-19 09:28) wrote:

There is a problem in the Kolab class in:
    function decodeDate($date)
    {
        if (empty($date)) {
            return 0;
        }

        list($year, $month, $day) = explode('-', $date);
        return gmmktime(0, 0, 0, $month, $day, $year);
    }

The problem is that assuming "0, 0, 0" as midnight is wrong here. The events
created by other Kolab 2 clients having entries like
<start-date>2005-04-22</start-date> show up from 2am to 2am at the next day
due to our GMT+2 (daylight saving) timezone.