[Tickets #12843] Re: Wrong timezone calculation with CalDAV

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12843
------------------------------------------------------------------------------
  Ticket             | 12843
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Wrong timezone calculation with CalDAV
  Queue              | Kronolith
  Version            | 4.1.4
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-02-06 01:45) wrote:

> I'm sorry, there is really a problem as you can see bellow.
> Can you please tell me how the timezone parsing is done in Horde  
> when importing ICS data ?

We take the TZID attribute from the DTSTART property and use it  
directly (assuming it's natively supported by PHP). We completely  
ignore the VTIMEZONE component.


> Did Horde use TZID and/or X-LIC-LOCATION line or use only DTSTART/DTEND ?
>
> As you can see bellow, when timezone in TZID and X-LIC-LOCATION  
> lines are different than timezone in DTSTART and DTEND lines it works.

Not that it matters, since the VTIMEZONE component is ignored when  
it's imported, but if the TZID attribute of DTSTART or DTEND is not  
also present in a VTIMEZONE, it's not a valid iCalendar file.

As with Jan, this file imports correctly for me. Perhaps your timezone  
database is outdated or corrupted? Either way, you will have to trace  
this yourself as no developer can reproduce it.