e-gaulue
commented
2 years ago Temporary workaround:
- Create a calendar for your own server agenda with your credential
- Restart Thunderbird to get this configuration written in the preferences
- Open the advance configurator and look for
calendar.registry.*.urikeys. If you know your URL structure, you should find the one you have just created. You can modify this uri entry to point to a collaborator agenda URI. - Restart Thunderbird
It does it, but it's not really "funny".
Is it hard to port TbSync caldav calendar discovery code to Thunderbird? If done, would it be considered as a new feature so we will have to wait for the next Thunderbird version or as a bugg fixe?
Reagrds,
Your environment
Thunderbird version: 102.2 Caldav Server: davical last version (with no configuration change since thunderbird update)
Expected behavior
DAV-4-Tbsync (or TbSync) used to list all shared agendas I could subscribe (often read only).
Actual behavior
Thunderbird just propose to subscribe to my own agenda corresponding to my credentials. Collaborators' agendas subscribed with DAV-4-Tbsync previous module are still available and work in the new version. But for new users, I can't set new shared agendas.
Steps to reproduce
Really hard to provide, all my Thunderbird have migrated to 102 now... I've got a backup if screenshot with previous behaviour is needed.
My bad, I just read:
As far as I understand, TbSync is coming back.
Is this the way to go? If yes will we need a new DAV-4-Tbsync?
Often people share their agendas but not their contacts (even if there are some use cases), so if just for agendas, should we rather wait for Thunderbird to better discover/list subscribable agendas?
Best regards,