[horde] possible solution for: All-day events with different timezone span days

[Steffen]

On Wed, 17 Jul 2013, Michael J Rubinsky wrote:

> Quoting Steffen <skhorde at smail.inf.fh-bonn-rhein-sieg.de>:
>> when I create an all-day event with timezone UTC within the GUI, but my 
>> default timezone is "Europe/Berlin" aka MEST aka UTC+2, the event span two 
>> days, because the event starts at 02:00. That's true, too, when the event 
>> gets synchronized to Android via ActiveSync or Lightning via CalDAV.
>> 
>> Do I create an all-day event with UTC in an ActiveSync Android device, the 
>> event is displayed as "all-day" event in the GUI as well, but do not span 
>> days.
>> 
>> The "trick" maybe is, that the all-day event of Android does not have no 
>> timezone at all or, to phrase it differently, the GUI displays the all-day 
>> event with the default timezone. In fact, as soon as I select "all-day" on 
>> the Android device the timezone selection becomes inaccessable.
>
> Correct. ActiveSync passes all time data for events (all-day or not) as UTC 
> (converted from the client's configured default timezone). Once imported into 
> Horde, it gets converted into the Horde default timezone.

Ah, I checked the DB then to see, where the differences are:

event_title 	event_start 	event_end 	event_allday 	event_timezone
L 11:00 	2013-07-18 09:00:00 	2013-07-18 10:00:00 	0 	Europe/Berlin
L allday 	2013-07-18 00:00:00 	2013-07-19 00:00:00 	1 
GUI allday 	2013-07-18 00:00:00 	2013-07-18 23:59:59 	0 	UTC
A allday 	2013-07-18 00:00:00 	2013-07-19 00:00:00 	1 
A 11:00 	2013-07-18 09:00:00 	2013-07-18 09:30:00 	0

"L" is lightning/CalDAV, "A" is Android/ActiveSync, "GUI" event created
via GUI.

The GUI-event is not marked as "allday", but is a 24h-event from 0 through
23:59 UTC. That's why it spans days.

Kind regards,

-- 
Steffen