accepting invitation does not add to google



Provider: GData
5 years ago
3 years ago


(Reporter: Derek, Unassigned)


Lightning 1.9.1




5 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36

Steps to reproduce:

I received an event invitation via a .ics file. I clicked on accept.

Actual results:

However clicking accept only adds the event to my local lightening calendar and does not update my google calendar with this event.

Expected results:

I would have expected that either I would be given a choice of which calendar to add the event to or it would have been added to both calendars.

I'm not sure if this is a known issue, I've seen both information that adjusting certain configuration settings should allow for this and other information that says it's not possible right now. It would be good if there was clear documentation about this, as it seems a key feature.

Comment 1

5 years ago
Hi, the Provider for Google Calendar extension doesn't support invitations and therefore can't be selected as the target calendar when accepting invitations. If there is only one other calendar that supports invitations it will be picked automatically by Lightning.

There already exists other bugs to investigate how Provider for Google Calendar extension can support invitations, e.g. Bug 684482.
There has been a major rewrite of the Provider for Google Calendar between version 0.32 and 1.0. A vast number of bugs have been fixed during this rewrite, therefore I am closing lots of old bugs that I think might either be fixed or no longer apply to the latest version.

Please read the updated FAQ [1] for details on known issues. If you can reproduce your issue with the latest version of the Provider for Google Calendar and you can't find an existing bug that handles your case, please reopen this issue.

Thank you for your understanding.

Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.