Bug 308808 - Gooogle Readonly calendars should be read-only in korganizer as well.
Summary: Gooogle Readonly calendars should be read-only in korganizer as well.
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Google Resource (show other bugs)
Version: 4.9
Platform: openSUSE Linux
: NOR normal
Target Milestone: 4.10
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-22 12:44 UTC by jens
Modified: 2012-10-23 09:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.10


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jens 2012-10-22 12:44:08 UTC
Hello there,

I'm using Google calendars together with the akonadi_googlecalendar_resource (the new one). In the akonadi system settings I have selecting my primary calendar and several others that I have configured in the Google web interface. Most of the other calendars are read-only.

Everything shows up nicely in Korganizer. Unfortunately all read-only calendars are shown like being editable. I can successfully modify an entry and it will be saved (to the akonadi cache I guess). The original calendar is of course not modified and hence my remote and local calendar are now out of sync.

Could you please present remote read-only calendars as not editable in korganizer? Read only calendars should also not be available when creating new entries. 

Regards,
Jens

Reproducible: Always

Steps to Reproduce:
1. Add a read-only calendar like ical resource to your Google calendar in the Google web interface.
2. Connect that google account as akonadi resource and select a read only calender.
3. Open Korganizer, modify and safe an existing item from a readonly calendar.
Actual Results:  
The item is saved and is modified (in akonadi). The remote calendar is not changed.

Expected Results:  
It should not be possible to edit or delete an item from a read-only calendar or to create new items in a read only remote calendar.

I don't know if this is really a korganizer issue, please let me know if this bug should be assigned to e.g. akonadi/akonadi google resource.
Comment 1 Allen Winter 2012-10-22 21:20:35 UTC
Dan,
Is this fixed with the new libkgapi?  In any case, I think this one for you
Comment 2 Daniel Vrátil 2012-10-23 09:26:22 UTC
This has been recently fixed in master and will be available in KDE 4.10.

http://commits.kde.org/kdepim-runtime/de752452016427318c013d6f4a662deb7ff7d0c4