No writable calendars are configured for invitations
A few weeks ago I set up Lightning (with great help from the TB forum participants) so that when I get meeting invitations by email, I could accept them and they would show up on my Google calendar. About a week ago, it stopped working.
When I receive an invitation, there is no button to accept. Instead, there is a notice that says "No writable calendars are configured for invitations, please check the calendar properties."
I made sure that the Google calendar is present and selected in the Lightning tab. I checked the calendar properties, and the email address where I receive meeting invitations (my work email) is set as the email address in the properties dialog box. And the check box is checked for switching the calendar on.
With thanks in advance, does anybody have any suggestions for getting TB/Lightning to work the way it did before? I.e. to let me accept meeting invitations and have them automatically added to my calendar?
Thanks!
Επιλεγμένη λύση
Good, can you then mark your post as 'Solution' for the topic? Thank you.
Ανάγνωση απάντησης σε πλαίσιο 👍 0Όλες οι απαντήσεις (6)
Still having this problem! If anybody can shed some light on this, many thanks in advance.
In the calendar properties make sure 'Read Only' is not checked.
Thanks for the reply. The menu item for "Calendar properties...." is dimmed, so I can't access it. But I can open and view the calendar window (or tab), and it is showing the Google calendar that I originally linked to.
I think this is solved. I downloaded an add-on called Provider for Google Calendars and installed it. After re-starting TB and bit of random clicking around on menu items that seem related to calendars, the Calendar properties menu item lit up, and I unclicked "Read Only" and now event invitations that arrive by email work again.
It's weird that this worked before, then suddenly stopped working, and I had to install an add-on to make it start working again. Very confusing....
Επιλεγμένη λύση
Good, can you then mark your post as 'Solution' for the topic? Thank you.
This problem is now solved!