I'm starting to use KOrganizer. My setup is the following:

Calendars:
- Outlook calendar at work
- Private calendar on my netbook

Syncihronization:
- "Google Calendar Sync": work calendar primary google calendar (called work, has to be primary, because Google Calendar Sync only syncs with the primary calendar)
- GCALDaemon: primary google calendar (work) work.ics on the netbook (loaded in KOrganizer)
- GCALDaemon: second google calendar (called private) private.ics on the netbook (loaded in KOrganizer)

Adding an appointment with KOrganizer to the private calendar adds that appointment also in my private google calendar. The problem is it also adds some kind of invite in the primary (work) google calendar for the same appointment. On a sync with "Google Calendar Sync" this private appointment gets added to my Outlook calendar at work, which is not what I want.

I have tried disabling invitations in Google Calendar, but it seems like it doesn't disable invitations from myself... I can remove myself as participant each time I add an appointment in KOrganizer and avoid the problem, but this adds a few steps to adding an appointment.

Can the participants feature be disabled in KOrganizer? I haven't found a way...
Is there some other good solution?
Has anyone else run into the problem?

This is also a bug, since Invitations should be stored in the same file as the appointment.
Please check to see if this has been filed / fixed already at bugs.kde.org

bcooksley wrote:This is also a bug, since Invitations should be stored in the same file as the appointment.
Please check to see if this has been filed / fixed already at bugs.kde.org

bugs.kde.org seems to be down. Has it been down for a long time? I tried to access it about a month ago, and it was down then too...

For a workaround, is it possible to disable the invitations feature?

bcooksley wrote:This is also a bug, since Invitations should be stored in the same file as the appointment.
Please check to see if this has been filed / fixed already at bugs.kde.org

Added the bug: https://bugs.kde.org/show_bug.cgi?id=186020