Closed
Bug 1420243
Opened 7 years ago
Closed 1 year ago
Some events (anniversary, death date) are not imported from a Nextcloud CalDAV server
Categories
(Calendar :: Provider: CalDAV, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: juergen.edner, Unassigned)
Details
Beside a birthday and a death date an anniversary date can be defined in a Nextcloud (v12.0.3) contact record, which are all automatically be used to create calendar events in a calendar called "contact birthdays". An anniversary event record, e.g. looks like this: BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Sabre//Sabre VObject 4.1.2//EN CALSCALE:GREGORIAN BEGIN:VEVENT DTSTAMP:20171031T145414Z DTSTART;VALUE=DATE:20001120 DTEND;VALUE=DATE:20001121 UID:2e1d9687-5a7c-4982-9ad3-bc2cae595476 RRULE:FREQ=YEARLY SUMMARY:Mr.Tom Jones (∞Â2000) TRANSP:TRANSPARENT BEGIN:VALARM TRIGGER;VALUE=DURATION:-PT0M ACTION:DISPLAY DESCRIPTION:Mr.Tom Jones (∞2000) END:VALARM END:VEVENT END:VCALENDAR If you now add this calendar to Lightning, its content, usually birthdays, are correctly displayed as e.g. "Mr.Tom Jones (*1970)", except death and anniversary records. These kind of records are not imported and displayed in the subscribed calendar. My assumption is, that the special characters which are used in the SUMMARY and DESCRIPTION fields to mark these kind of events, is causing a problem during the import. Anniversary events are usually containing the infinity symbol (hex:e29a) in front of the year, e.g. "(∞Â2000)", death dates are containing a cross symbol (hex:e280) in front of the year, e.g. "(†2010)". I've checked the local calendar database but the records have definitely not been imported. I've also checked the web servers log file and the error console within Thunderbird but no errors were logged during a synchronization attempt.
Updated•2 years ago
|
Severity: normal → S3
Comment 1•1 year ago
|
||
Reporter,
Does this issue still fail for you when using version 102?
If it does, please comment with current steps to reproduce.
Whiteboard: [closeme 2023-01-20]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2023-01-20]
You need to log in
before you can comment on or make changes to this bug.
Description
•