[Tickets #13498] Re: Exception of recurring event with timezone and CalDAV client

noreply at bugs.horde.org noreply at bugs.horde.org
Tue Aug 26 11:46:54 UTC 2014


Ticket-URL: https://bugs.horde.org/ticket/13498
  Ticket           | 13498
  Aktualisiert Von | olaf at boppenhaeger.de
  Zusammenfassung  | Exception of recurring event with timezone and CalDAV
                   | client
  Warteschlange    | Kronolith
  Version          | 4.2.1
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |

olaf at boppenhaeger.de (2014-08-26 11:46) hat geschrieben:

> Cannot reproduce, works fine with and without explicitly set event timezones.

I 've just now testet this with the Evolution CalDAV client.
It's the same behavior as with Thunderbird/Lightning.

Are you sure the base event has really an explicit timezone set in database?
My timezone is Europe/Berlin.

How I can always reproduce this:
- create a recurring event e.g. daily from monday to sunday at 12pm  
with expizit timezone set (with CalDAV client)
- check in database or web GUI if timezone is set really set
- create an exception event e.g. on wednesday to 4pm with expizit  
timezone set (also with CalDAV client)
- now, this exception is lost in my case

If your exception isn't lost in your calendar please check again in  
database or web GUI if the timezone is really set to all events.

While testing with the Evolution client i noticed that it works fine,  
if the base event hasn't set a expizit timezone but the exception  
event has one.
If the the timezone of the base event is set after creating an  
exception event it works also.
But if the exception event is then altered again it is lost.

And another strange behavior occurs on the CalDAV client. If i create  
the base and exception event without timezone it works. But if i  
change the exception event a second time (e.g. to another time) it is  
also lost although there is no timezone set.

I hope i could help you to reproduce this issue.

More information about the bugs mailing list