| Summary: | Issues to Export / Import Calendars | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | Rafael Fernandes <rfernandes> |
| Component: | Akonadi | Assignee: | David Jarvie <djarvie> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | ||
| Priority: | NOR | ||
| Version: | 2.11.4 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Rafael Fernandes
2017-09-20 14:23:58 UTC
The export bug was fixed in KAlarm 2.11.12, which was released in KDE Applications 16.12.1. Importing displaying.ics doesn't seem useful, since it is essentially a temporary file which just contains alarms which are currently being displayed. Its only use is to enable KAlarm to redisplay the alarms after a logout or a crash. So I don't propose to try to make it possible to import that file. I'll look into the import problem with expired.ics. If you need to import expired.ics now, you could use the following workaround: Copy expired.ics to another temporary file. Using a text editor, edit that temporary file and remove the 5 lines at the start from BEGIN:VCALENDAR down to (and including) the line beginning X-KDE-KALARM-VERSION. Also remove the last line END:VCALENDAR. Copy this temporary file onto the other computer. On the other computer, edit its expired.ics and insert the contents of the temporary file immediately before the last line END:VCALENDAR. You should then see the copied expired alarms in KAlarm in the new computer. If you don't see them, you may need to restart Akonadi, or alternatively quit KAlarm and Akonadi before editing the file. Let me know if you need to do this but don't know how to. Hi David. First, Thank you for your attention. " On the other computer, edit its expired.ics and insert the contents of the temporary file immediately before the last line END:VCALENDAR. My expired.ics file only has the following lines: BEGIN: VCALENDAR PRODID: - // K Desktop Environment // NONSGML libkcal 4.3 // EN VERSION: 2.0 X-KDE-ICAL-IMPLEMENTATION-VERSION: 1.0 X-KDE-KALARM-VERSION: 2.7.0 END: VCALENDAR If I delete it according to your instructions I will have to delete all of them and the document will be empty. That's right? Sorry I didn't reply sooner, but I somehow missed your update. You're right. If expired.ics is empty on the new computer, you don't need to do any editing - you can simply copy expired.ics from the old computer and replace the empty one on the new computer. (In reply to David Jarvie from comment #3) > Sorry I didn't reply sooner, but I somehow missed your update. > > You're right. If expired.ics is empty on the new computer, you don't need to > do any editing - you can simply copy expired.ics from the old computer and > replace the empty one on the new computer. OK David, I'll try this alternative. Very Thanks. I tested the import of an expired alarms calendar with the latest version of KAlarm (version 2.12.5, which will soon be released as part of KDE Applications 19.08). This worked correctly, both when importing into an empty expired.ics and when expired.ics contained existing alarms. If you see this problem again, please reopen this bug. *** This bug has been marked as a duplicate of bug 374337 *** |