Bug 232725 - korganizer doesn't offer to choose among akonadi resources when saving a new event
Summary: korganizer doesn't offer to choose among akonadi resources when saving a new ...
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-30 17:52 UTC by Roman Zimmermann
Modified: 2011-05-25 15:18 UTC (History)
2 users (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 Roman Zimmermann 2010-03-30 17:52:04 UTC
Version:           current 4.4 branch (using Devel)
Compiler:          gcc-4.3.4 
OS:                Linux
Installed from:    Compiled sources

Normally when creating a new event in korganizer while there is more than one resource active it offers a dialog in which you can choose in what resource to store the new event.

In this respect all akonadi resources are handled as one resource. The new event is always stored in the first akonadi resource - regardless of it's state (active or inactive).

Steps to reproduce:
1. Have more than one akonadi resource.
2. Create a new event.
3. choose akonadi resource if dialog is displayed (it is only displayed if there is at least one non-akonadi resource)

Expected result:
korganizer offers a choice among akonadi resources.

Actual result:
The new event is always saved to the first akonadi resource.

The problem is aggravated by the fact that the activeness of the resources is completely ignored. Therefore it is not possible to change the behavior except by removing all but one akonadi resource.


Please tell me if there is anymore information needed to reproduce this misbehavior.
Comment 1 Ingo Ratsdorf 2010-07-27 22:47:34 UTC
Even worse, when you only have akonadi resources in korganizer. You won't be able to create any event at all because the selection box for calendars is EMPTY. So you cannot create any events.
I am using the akonadidavresource and have one akonadi resource (DAV) with three calendars. When it was only one calendar, everything worked nicely. Since I have added another one, I cannot create events any more because Korganizer recognises the fact the the default calendar (akonadi) has three resources, so asks for the location but fails to fill the selection box. SERIOUS.

That makes the whole idea of collaboration any more than one calendar somewhat silly.

KOrganizer Version 4.4.5
Using KDE Development Platform 4.4.92 (KDE 4.4.92 (KDE 4.5 RC2))
Comment 2 Ingo Ratsdorf 2011-05-25 04:44:10 UTC
Hi.

Has there been any update on this?
The problem relates back to the inability of Kontact to show and select in recursive Akonadi subfolders, ie. only on one level down from root.

BUT: Akonadi groupdav resource creates a folder groupdav resource and has subfolders for contacts, todos and events.
Those are not visible to Kontact because one level to low...

Has that been addressed?
Comment 3 Sergio Martins 2011-05-25 15:18:46 UTC
Fixed in master and 4.6rc1.