Bug 301559 - New calendars in kontact are not created on the DAV server
Summary: New calendars in kontact are not created on the DAV server
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: 1.7.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-10 07:47 UTC by Médéric Boquien
Modified: 2017-01-07 22:37 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Médéric Boquien 2012-06-10 07:47:50 UTC
Hello,

I have an owncloud installation with a caldav resource. The sync works fine both ways with one exception. When i create a new calendar in korganizer, it never gets created in owncloud. Basically the only way to create a calendar seen everywhere is to create it through the owncloud web interface.

Reproducible: Always

Steps to Reproduce:
1. Open korganizer
2. Create a calendar
3. Sync the resource
Actual Results:  
The new calendar is not synced with the DAV resource and remains only local.

Expected Results:  
The new calendar should be created and synced in the DAV resource and visible in all synced devices.

I do not know whether it is an owncloud or an akonadi issue.
Comment 1 Grégory Oestreicher 2012-10-18 07:33:50 UTC
Hi,

Unfortunately this is a known limitation of the resource. Fixing this would require changes into kdelibs to add the MKCALENDAR method, but afaik changes are no longer accepted as all efforts go into the KDE frameworks.

Still setting the status to 'NEW', as this should be fixed, and hopefully will.

Cheers,
Grégory
Comment 2 Denis Kurz 2016-09-24 20:39:15 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:37:06 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.