| Summary | Exception(s) of recurring event isn't exported if timezone is set |
| Queue | Kronolith |
| Queue Version | 4.2.0 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | olaf (at) boppenhaeger (dot) de |
| Created | 07/15/2014 (4111 days ago) |
| Due | |
| Updated | 08/04/2014 (4091 days ago) |
| Assigned | 07/29/2014 (4097 days ago) |
| Resolved | 07/29/2014 (4097 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
If such a exception event is made with a CalDAV client
(Thundebird/Lightning), this is not created on horde/server side.
The event for this day is "lost" at all.
iCal is working fine now!
Taken from
State ⇒ Resolved
commit 7f155a0d0ae86d953ff6a2c1c1bc814eb57359f8
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Tue Jul 29 12:47:43 2014 -0400
Bug: 13369Fix exporting ics when event contains exceptions ANDexplicit timezone data.
kronolith/lib/Event.php | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
http://github.com/horde/horde/commit/7f155a0d0ae86d953ff6a2c1c1bc814eb57359f8
commit 6797ab56d8e382fc0a26f37a436a3c2b893b16db
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Tue Jul 29 12:47:43 2014 -0400
Bug: 13369Fix exporting ics when event contains exceptions ANDexplicit timezone data.
kronolith/lib/Event.php | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
http://github.com/horde/horde/commit/6797ab56d8e382fc0a26f37a436a3c2b893b16db
State ⇒ Assigned
Assigned to
Assigned to Michael Rubinsky
being imported as a 6 hour event (6am to 2pm) instead of a two hour
event.
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
New Attachment: recurring event with exception.ics
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Exception(s) of recurring event isn't exported if timezone is set
Type ⇒ Bug
it has a timezone set.
If the exception event has no timezone set, all works fine.
The display in the web surface and ActiveSync clients is ALWAYS correct!
For smarter testing please use the attached ICS-file for import to a
new calendar and afterwards exporting it again to a new ICS-file.
How to reproduce in web surface:
Create a weekly recurring event for e.g. 4 weeks. Set timezone to
Europe/Berlin.
Then create an exception event for e.g. the 2nd recurrence. Make sure
the timezone is also set to Europe/Berlin.
Edit the exception event to set the timezone again to Europe/Berlin
(while creating the exception event the timezone wasn't set correctly!).
When exporting the calender via ics-file or subscribing to this
calendar via ICS or CalDAV the exception event is not transferred.
How to reproduce with a client like Thunderbird/Lightning:
Create an event and an exception like above within the client.
The client sets/transmit the timezone of the exception event
automatically with the client default settings (e.g. Europe/Berlin).
If the client is subscribed to the calendar via ICS the behavior is as above.
If the client is subscribed to the calendar via CalDAV then the
exception event is NOT created at all.