[Tickets #13866] Re: CalDAV PUT parses multiple VTIMEZONE data incorrectly, even its own ones

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/13866
------------------------------------------------------------------------------
  Ticket           | 13866
  Aktualisiert Von | kmh at hamich.net <kmh at hamich.net>
  Zusammenfassung  | CalDAV PUT parses multiple VTIMEZONE data incorrectly,
                   | even its own ones
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


skhorde at smail.inf.fh-bonn-rhein-sieg.de (2015-02-23 14:18) hat geschrieben:

With RDATE entries are returned that exist in the requested $year and  
in $year-1.

With RRULE only one $result is returned, the entry of $year. So, if  
the caller wants to know the timezone for the 2nd Feb 2015, the  
timestamps of daylight and standard time of _2015_ are returned, which  
neither does apply! Daylight is in March, standard in Oct.

Attached patch returns the entry for $year and $year-1 for RRULE, too.  
Which is not 100% correct either, but mimmicks the idea of RDATE and  
will cover the situation I faced right now.



skhorde at smail.inf.fh-bonn-rhein-sieg.de (2015-02-23 14:18) hat  
hochgeladen: caldav_vtimezone_bug13866.patch.bz2

https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=caldav_vtimezone_bug13866.patch.bz2&ticket=13866&fn=%2Fcaldav_vtimezone_bug13866.patch.bz2