| Summary: | With caldav backend, korganizer always tries to save full calendar when one event is changed | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | Alain Knaff <kde> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | smartins |
| Priority: | NOR | ||
| Version First Reported In: | 4.4.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
KResources are unmaintained. Use an akonadi resource. |
Version: 4.4.3 (using KDE 4.4.6) OS: Linux In a caldav calendar ("calendar in remote file" with http:// location), korganizer tries to store the entire calendar (all events as a single ical entry) if one event is changed and added. This is (rightfully) rejected by most caldav backends, such as davical. Reading (displaying) a caldav calendar works fine Reproducible: Always Steps to Reproduce: 1. Create calendar with caldav backend ("Calendar in remote file", "http://www.hitchhiker.org.lu/caldav/caldav.php/alain/home/") 2. Reload calendar => calendar is displayed correctly 3. Change an event => Access was denied while attempting to upload http://www.hitchhiker.org.lu/caldav/caldav.php/alain/home/. Actual Results: Access was denied while attempting to upload http://www.hitchhiker.org.lu/caldav/caldav.php/alain/home/. (because it sends the entire calendar to the backend, rather than just the event that was actually changed...) Expected Results: It should update just the one entry that was changed OS: Linux (x86_64) release 2.6.32-32-generic Compiler: cc