![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
I cannot send out an event invitation.
I am trying to send out an event invitation through Lightning 4.0.2. When I select the attendees in the "Invite Attendees" dialog box (that part works fine) and return to the "Edit Event" dialog box, my attendees are listed, but the "Notify Attendees" and "Separate invitation per attendee" checkboxes are greyed out with the "Notify Attendees" checkbox checked. If I then click "Save and Close", the event never sends and invite, and if I re-open the event, any attendees I have invited are no longer listed. I've searched the forums exhaustively for advice but couldn't find a solid solution.
System Configuration Details: Windows 10 Thunderbird 38.2.0 Lightning 4.0.2 Connecting to a Google calendar The problem is present regardless of whether using CalDAV or Provider for Google 1.0.4 to access calendar. Events can read and write on Google calendar normally -- I just can't send out invites.
Any assistance would be most appreciated. Thank you!
Усі відповіді (2)
A non-ideal workaround for others who may have the same issue: Until there's a solution to this, I used the "Google Calendar Tab 3.9" add-on so that I can access my Google Calendar through Thunderbird and invite people to events from there. Lightning does pick up that I have sent out invites and tracks accepts and declines of invites as usual when I sync calendars, but I still can't send out an event invite through Lightning, which would be preferred. Any help on this would still be most appreciated, and if I come across a solution in the meantime, I'll post it here. Thanks!
Update: It looks like with the recent update to Lightning 4.0.2.1 the problem with sending out the invitations has been resolved. However, the "Notify Attendees" and "Separate invitation per attendee" boxes are still greyed out. For me it's working fine now, but others may need the functionality that the greyed out boxes provide. Thanks for addressing the issue!