Summary: | [testcase] EXDATE ignored if Time Component present | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | George Sexton <gsexton> |
Component: | recurrence | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | finex, kde, smartins |
Priority: | NOR | Keywords: | testcase, triaged |
Version: | 3.2.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
George Sexton
2004-07-12 17:52:47 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. Tried this ical entry with 4.1.3 on Kubuntu Intrepid. As specified in EXDATE;TZID=America/Denver:20040728T180000 the event is not listed for that date in the graphical calendar view. When opening the Recurrence editor for this entry, however, no date is listed in the "Exceptions" box. The original reporter is probably correct in assuming that the time information in EXDATE causes this because it is only possible to select a date in this box and a new EXDATE entry comes in the form EXDATE;VALUE=DATE:20040721 and is listed as expected in both places. This format also causes the problem that if the event occurs on a different day in another time zone that the local day has to be added to the exceptions list rather than the day on which the recurrence is listed in the timezone of the entry. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Thanks for making me smile. A bug report from 12 years ago... I tested with KOrganizer v 4.14.10 using KDE version 4.14.18 on OpenSUSE Leap 42.1 and it works as expected. |