[Tickets #12773] Re: Thunderbird lightning caldav serial event time failure with summer/wintertime change

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12773
------------------------------------------------------------------------------
  Ticket             | 12773
  Updated By         | rs at sys4.de
  Summary            | Thunderbird lightning caldav serial event time failure
                     | with summer/wintertime change
  Queue              | Kronolith
  Version            | 4.1.3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


rs at sys4.de (2014-02-06 07:41) wrote:

>> Now Kronolith internally uses UTC to represent the event. That is
>> beneficial for many purposes. But the Kronolith developers seemingly
>> didn't think about *repeated* events here. If we repeat an event with
>> *fixed* time in UTC (every repetition is at 19:00 in UTC), this will
>> mean a non-fixed time in local timezones.
>
> We *absolutely* take into account recurrence series. We explicitly  
> add the timezone information to the vCalendar when we are outputting  
> recurring series. You can see this in  
> Kronolith_Event::toiCalendar(). If the event is being output in UTC,  
> then that means that either the event's timezone was explicitly set  
> to UTC or there was no explicit timezone set and the default  
> timezone for the user in question is UTC.
>

Hi Michael , whatever the reason is, it need to be fixed, cause its a  
real showstopper for using Horde with Thunderbird Lightning. There is  
a ticket at Mozilla about it too, so what can be done to get this fixed.