Bug 308779 - Importing from vCalendar format results in deleting data from file
Summary: Importing from vCalendar format results in deleting data from file
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: import/export (other bugs)
Version First Reported In: 4.9.2
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: Sergio Martins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-22 01:33 UTC by Marcus Harrison
Modified: 2017-01-07 22:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Harrison 2012-10-22 01:33:18 UTC 
Exporting visible events using File --> Export --> Export as vCalendar... doesn't export events properly. Opening the file in KWrite reveals the following:

BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN
VERSION:2.0
END:VCALENDAR

Of course, attempting to import this back into KOrganizer results in no new events being added. iCalendar and HTML exporters work as expected.

Reproducible: Always
Comment 1 Marcus Harrison 2012-10-29 11:26:12 UTC 
I was wrong: the export successfully populates the file with events, visible in a text editor. However, clicking on the file to open it in KOrganizer, or using File-->Import-->Import Calendar... to import the file as a new Akonadi calendar resource deletes all events from the file, resulting in the contents I posted above being visible in a text editor.

This is a serious issue as it results in data loss.
Comment 2 Denis Kurz 2016-09-24 18:46:54 UTC 
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.
Comment 3 Denis Kurz 2017-01-07 22:38:47 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.