[Korganizer-devel] [Bug 285405] New: Exceptions in occurence: problem with ics format?

[kaouete]

https://bugs.kde.org/show_bug.cgi?id=285405

           Summary: Exceptions in occurence: problem with ics format?
           Product: korganizer
           Version: 4.7
          Platform: Archlinux Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: recurrence
        AssignedTo: korganizer-devel at kde.org
        ReportedBy: kaouete at crazydwarves.org


Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

Hi,

I have been using korganizer with akonadi groupware connector.
I sync with a SOGo caldav server.

I don't think the problem is directly linked to SOGo or akonadi, but it is
where it is visible.

Reproducible: Always

Steps to Reproduce:

The problem is as following:

If I add a recurring event for 5 consecutive days in korganizer, the ical
content is as follow (as given by akonadi console in the raw payload field):
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 3.2//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:20111031T162950Z
ORGANIZER;CN="Victor Noël":MAILTO:victor.noel at irit.fr
DTSTAMP:20111031T162929Z
UID:8dba3f03-2888-4d3e-9e7c-e4b7d7e9c0fd
LAST-MODIFIED:20111031T162929Z
SUMMARY:Test Rec
RRULE:FREQ=DAILY;COUNT=5
DTSTART;TZID=Europe/Paris:20111107T170000
DTEND;TZID=Europe/Paris:20111107T180000
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR

Then, if I add an exception from korganizer for the 2nd day, the content is as
follow:
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 3.2//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:20111031T163056Z
ORGANIZER;CN="Victor Noël":MAILTO:victor.noel at irit.fr
DTSTAMP:20111031T162929Z
UID:8dba3f03-2888-4d3e-9e7c-e4b7d7e9c0fd
SEQUENCE:1
LAST-MODIFIED:20111031T162929Z
SUMMARY:Test Rec
RRULE:FREQ=DAILY;COUNT=5
EXDATE;VALUE=DATE:20111108
DTSTART;TZID=Europe/Paris:20111107T170000
DTEND;TZID=Europe/Paris:20111107T180000
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR

In particular the "EXDATE;VALUE=DATE:20111108" should be noticed.

But, with this information, the exception is not shown in SOGo or on my phone
where I sync too (this is why I started investigating this thing :).

Now, if I decide to add an exception from SOGo, this is the content of the
event:
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 3.2//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:20111031T163228Z
ORGANIZER;CN="Victor Noël":MAILTO:victor.noel at irit.fr
DTSTAMP:20111031T162929Z
UID:8dba3f03-2888-4d3e-9e7c-e4b7d7e9c0fd
SEQUENCE:2
LAST-MODIFIED:20111031T162929Z
SUMMARY:Test Rec
RRULE:FREQ=DAILY;COUNT=5
EXDATE;VALUE=DATE:20111108
EXDATE:20111109T160000Z
DTSTART;TZID=Europe/Paris:20111107T170000
DTEND;TZID=Europe/Paris:20111107T180000
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR

Notice the newly added line and the way it is formatted.
EXDATE:20111109T160000Z

Now, everywhere this exception is shown: in SOGo, on my phone and in
korganizer.
Also, in korganizer, the previously added exception is still present, and if I
edit the event (for all recurrence), then I can ONLY see the first exception in
the exception list and not the one added from SOGo.


Expected Results:  
So, based on that, it seems to me that there is two problems with korganizer:
1) the way it store the exception information is incorrect, or at least not the
standard way (or SOGo and android calendar are wrong, this must be verified
first).
2) exceptions shown in the calendar must also be visible in the edit window.

I'm available to do more tests if necessary :)

Thank you very much!

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.