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

* Your Email Address
* Spam protection	Enter the letters below: . .. ,.___.. ..__ \|_/ \./ \| \|\ \|\| \ \| \ \| \| \| \\|\|__/
Comment	> 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. > >
Attachment
Watch this ticket