Summary | incorrect placement of VTIMEZONE component in ical export |
Queue | Kronolith |
Queue Version | 4.0.0 |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | jan (at) horde (dot) org |
Requester | rella (at) myrho (dot) net |
Created | 11/03/2012 (4639 days ago) |
Due | |
Updated | 11/05/2012 (4637 days ago) |
Assigned | |
Resolved | 11/05/2012 (4637 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | 4.0.1 |
Patch | No |
State ⇒ Resolved
Priority ⇒ 2. Medium
Milestone ⇒ 4.0.1
commit 2c527775cd4a7b3130ded1472a7c0c0e44ded27b
Author: Jan Schneider <jan@horde.org>
Date: Mon Nov 5 18:07:02 2012 +0100
[jan] Fix incorrect nesting of VTIMEZONE components when
exporting to iCalendar (
Bug #11636).kronolith/docs/CHANGES | 2 ++
kronolith/lib/Event.php | 2 +-
kronolith/package.xml | 2 ++
3 files changed, 5 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/2c527775cd4a7b3130ded1472a7c0c0e44ded27b
Priority ⇒ 3. High
New Attachment: 03YTXqM1A09Qk_HL6hGn9-A.ics
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ incorrect placement of VTIMEZONE component in ical export
Type ⇒ Bug
State ⇒ Unconfirmed
The ical validator at [1] states for the example ical file in
attachment: "The time zone with the TZID 'Europe/Vienna' was not
found." and suggests the resolution "to ensure the corresponding
VTIMEZONE for TZID 'Europe/Vienna' is contained in the calendar."
However, a VTIMEZONE component is present but it seems to be placed
incorrectly. The RFC2445 [2] on ICalendar says on p. 61: "The
"VTIMEZONE" calendar component cannot be nested within other calendar
components." but the generated ical file of kronolith places VTIMEZONE
within a VEVENT component.
Putting the VTIMEZONE component after the VEVENT component by hand and
revalidating this ical file again yields no more errors.
[1] http://icalvalid.cloudapp.net/
[2] http://www.ietf.org/rfc/rfc2445.txt