Bug 88201 - It should be possible to change the ressource backend for already entered events, todos, contacts
Summary: It should be possible to change the ressource backend for already entered eve...
Status: RESOLVED DUPLICATE of bug 72531
Alias: None
Product: korganizer
Classification: Applications
Component: groupware (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Cornelius Schumacher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-27 10:44 UTC by Stéphane Magnenat
Modified: 2004-10-03 17:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed 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 Stéphane Magnenat 2004-08-27 10:44:37 UTC 
Version:           unknown (using KDE 3.3.0,  (3.1))
Compiler:          gcc version 3.3.4 (Debian 1:3.3.4-7)
OS:                Linux (i686) release 2.6.7-1-686

It should be possible to change the ressource backend for already entered events, todos, contacts.

I have all my PIM stuff in local and I would like to switch to an IMAP resource backend. It is currently possible only for new stuff; it is impossible to change the backend for already entered events, todos, contacts.

Kontact/KDE PIM is a great suit of software, thanks.

Steph
Comment 1 Reinhold Kainhofer 2004-10-03 17:25:00 UTC 
What you can do (and what I did when moving from local file to IMAP resource): 
1) Add the IMAP resource
2) Disable the file resource, and leave only the IMAP resource on (set it as standard resource)
3) Import the local file (Menu item "File->Import->Import from Calendar"): ~/.kde/share/apps/korganizer/std.ics
4) All the incidences from std.ics will be imported to the IMAP resource.

This works if you want to move all incidences.
The wish to move single incidences to a different resource is already reported as bug #72531.

So, I think this wish is either already implemented, or a duplicate of 72531.

Cheers,
Reinhold

*** This bug has been marked as a duplicate of 72531 ***