CALDAV calendar will not stay read only
Categories
(Calendar :: Provider: CalDAV, defect)
Tracking
(Not tracked)
People
(Reporter: marcausl, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
Subscribed to a calendar in my GMAIL account. Set it read only. Restarted TB.
Actual results:
After restart, the calendar almost immediately switches back to read/write
Expected results:
If I set a calendar read only, it should stay read only.
Comment 1•3 years ago
|
||
I don't see anywhere in the Google Calendar settings on the web where I can set a calendar as read only, so setting it as read only in Thunderbird may not work since it is a network calendar.
I'm subscribed to my Google Calendar, the US Holidays and my roommates calendar.
Made all of them read only, restarted Thunderbird, and the only one that stayed read only was the holiday calendar, which I would expect to be read only.
Reporter | ||
Comment 2•3 years ago
|
||
I hope this can be "fixed". It's an issue because with more than one readwrite calendar event creation can get confused. The fact that it "works" until restart implies that the mechanism is there.
Comment 3•3 years ago
|
||
What version did it last work in?
I can mark my Google calendar as read only in Thunderbird 91.2.0, try to create an event and that calendar doesn't appear as a choice in the Calendar field.
It does lose read only status upon a restart.
I don't see any mechanism to make the calendar read only on the web interface, so I suspect Google doesn't get the hint and reverts it to read/write upon a Thunderbird restart.
Comment 4•3 years ago
|
||
Maybe there is another bug report for this because I can make my Google calendar read only in Thunderbird 94.0b3 and 95.0a1 on Windows 10, and it sticks after restarting. I quit and restarted each several times,
Doesn't stick using Thunderbird 91.2.0.
Reporter | ||
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Thanks for supplying the information requested.
Comment 6•3 years ago
|
||
Will be fixed in Thunderbird 92.2.1.
Description
•