Az oldal korlátolt funkcionalitással fog rendelkezni, amíg elvégezzük a felhasználói élményt javító karbantartást. Ha egy leírás nem oldja meg a problémáját, és kérdést tenne fel, akkor a támogatási közösségünk a @FirefoxSupport Twitter oldalon tud segíteni, vagy az /r/firefox oldalon a Redditen.

Avatar for Username

Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

Google Calendars suddenly "read-only" - v68 & latest

  • 1 válasz
  • 1 embernek van ilyen problémája
  • 2 megtekintés
  • Utolsó üzenet ettől: user2817436

user2817436
user2817436
more options

Suddenly, when I attempt to modify or create a calendar event in Thunderbird, I'm presented with an error message essentially recommending that I set the calendar to "read-only" (and TBird automatically sets it that way). If I turn off the "read-only" checkbox and try the event modification again, same problem. I uninstalled TBird and tried going back to v68. I created an entirely new profile and -still- get the same problem.

I then tried Microsoft's Calendar app; no problem. Then I tried a number of other integrated clients (em Client, Mailbird, Hexamail Flow) and -all- worked properly with my Google calendar. On my other PC, TBird is working perfectly with Google calendar. On both machines, all the eMail accounts in TBird send/receive as expected.

I was thinking the new profile would resolve things but are there other files TBird puts in places that might be pooched? Or is this something that a Reset of Windows (reinstall with keeping my data in place) might resolve?

Advice welcomed. Thanks,

Barry

Suddenly, when I attempt to modify or create a calendar event in Thunderbird, I'm presented with an error message essentially recommending that I set the calendar to "read-only" (and TBird automatically sets it that way). If I turn off the "read-only" checkbox and try the event modification again, same problem. I uninstalled TBird and tried going back to v68. I created an entirely new profile and -still- get the same problem. I then tried Microsoft's Calendar app; no problem. Then I tried a number of other integrated clients (em Client, Mailbird, Hexamail Flow) and -all- worked properly with my Google calendar. On my other PC, TBird is working perfectly with Google calendar. On both machines, all the eMail accounts in TBird send/receive as expected. I was thinking the new profile would resolve things but are there other files TBird puts in places that might be pooched? Or is this something that a Reset of Windows (reinstall with keeping my data in place) might resolve? Advice welcomed. Thanks, Barry

Összes válasz (1)

user2817436
user2817436 Kérdés tulajdonosa
more options

I think my problem is resolved but I'm not even sure why I ended up here in the first place when everything was working and then it just wasn't. I used the TBSync and the "Provider for CalDAV & CardDAV" Add-ons. I think I had them as part of my working TBird system but I KNOW I didn't do the configuration (before) the latter Add-on required now. As I say, it WAS working and then stopped working. When it stopped working, the Addressbook continued to sync properly but the Calendars became read-only. I wiped out everything (app and the entire TBird folder which contained all the profiles I had created with the various re-installations of v63 up to v73). The latest installation of v73 finally began working properly after I managed to get CalDAV/CardDAV Add-on properly configured.

What I can't figure out is why it was working and then suddenly stopped. The more I think about it, I'm suspecting the older TBird version I had been using had some older Add-ons that did the Addressbook/Calendar syncing and, when TBird updated from 73.0 to 73.1(?), it broke something.

At least I have it all back now. I'll call this issue resolved. Sorry for the fire drill.