Sync for caldav not working after update to Thunderbird 60
After I updated from Thunderbird 52.9 to 60 enlightenment stopped working with all caldav calendars on my nextcloud-instance. It doesn't synchronize anymore and doesn't even show that it doesn't. As soon as I downgrade to Thunderbird 52.9 and Enlightenment 5.4 all is good. I don't believe the problem being the nextclouds fault because the syncing is working with all android apps, Evolution and CLI tools too. I tested with a now profile on Thunderbird 60. But that doesn't help. I only get empty calenders because of the sync-problems
被采纳的解决方案
I believe this is the CalDAV known-issue, it's a NextCloud problem. It's been reported in this issue, there is a workaround:
- Go to the config editor (Settings -> Advanced -> General -> Config Editor)
- Search for network.cookie.same-site.enabled
- Set it to false
For your own security you should set it back to true once this issue is resolved.
This was also mentioned in the release notes (very bottom of https://www.thunderbird.net/en-US/thunderbird/60.0/releasenotes/ )
定位到答案原位置 👍 4所有回复 (3)
选择的解决方案
I believe this is the CalDAV known-issue, it's a NextCloud problem. It's been reported in this issue, there is a workaround:
- Go to the config editor (Settings -> Advanced -> General -> Config Editor)
- Search for network.cookie.same-site.enabled
- Set it to false
For your own security you should set it back to true once this issue is resolved.
This was also mentioned in the release notes (very bottom of https://www.thunderbird.net/en-US/thunderbird/60.0/releasenotes/ )
Thank you and sorry that I didn't read all through the release note.
Fabián Rodríguez said
I believe this is the CalDAV known-issue, it's a NextCloud problem. It's been reported in this issue, there is a workaround:For your own security you should set it back to true once this issue is resolved. This was also mentioned in the release notes (very bottom of https://www.thunderbird.net/en-US/thunderbird/60.0/releasenotes/ )
- Go to the config editor (Settings -> Advanced -> General -> Config Editor)
- Search for network.cookie.same-site.enabled
- Set it to false
Same problem here, tried the workaround to no avail. Is there anything else that can be done aside of downgrading?