| Summary | unparsable exceptions for recurring events due to datetime instead of date |
| Queue | Kronolith |
| Queue Version | 3.0.16 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | jan (at) horde (dot) org |
| Requester | Karl-Ulrich.Bamberg (at) campus (dot) lmu (dot) de |
| Created | 05/11/2012 (4803 days ago) |
| Due | |
| Updated | 10/25/2012 (4636 days ago) |
| Assigned | 05/15/2012 (4799 days ago) |
| Resolved | 10/25/2012 (4636 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | 4.0.0 |
| Patch | No |
Milestone ⇒ 4.0.0
Assigned to Jan Schneider
State ⇒ Assigned
New Attachment: horde_Icalendar.diff
the attached FIX (only 2 lines), changes the behavior of Hordes
Icalender export system to use dates (Ymd) instead of datetimes. This
is what at least Kontact 3 and 4 expect. We will test tomorrow with
Thunderbird. Is there any reason why RDATE and EXDATE should be
datetimes?
Kind Regards,
Karl-Ulrich Bamberg
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ unparsable exceptions for recurring events due to datetime instead of date
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
The Recurrences are recognized correctly. This is visible in the Webinterface.
However, a download of the calender with Kontact for example does not show the
exception.
RRULE ist set correctly.
EXDATE is available but shows for an exception an May 27th:
EXDATE:20120526T220000Z
But actually there should only be the Date, not the time (like it was before):
EXDATE:20120527
Thanks and best regards
Karl-Ulrich Bamberg