| Summary: | Non-standard iCal fields cannot be interpreted by third-party applications: Do not use them non-standard iCal fields | ||
|---|---|---|---|
| Product: | [Applications] zanshin | Reporter: | Erik Quaeghebeur <bugs.kde.org> |
| Component: | general | Assignee: | Kevin Ottens <ervin> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | mbensi, openmail+kde |
| Priority: | NOR | ||
| Version First Reported In: | 0.5.0 | ||
| Target Milestone: | already done | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Custom akonadi date field used for recurring tasks | ||
|
Description
Erik Quaeghebeur
2018-12-05 15:30:11 UTC
Created attachment 149950 [details]
Custom akonadi date field used for recurring tasks
Same issue here. iCal fields for the task:
DUE;VALUE=DATE:20220501
DTSTART;VALUE=DATE:20220501
...
X-KDE-LIBKCAL-DTRECURRENCE;VALUE=DATE-TIME;TZID=Europe/Berlin:
20220626T000000
---
Since the custom field is used for recurring tasks these don't sync properly to non-akonadi devices and applications.
The iCal backend should use the standard iCal date field instead of X-KDE... to be compatible with other clients.
|