Open georgehrke opened 4 years ago
cc @tcitworld cc @rullzer for feature planning :)
One of the biggest issue when it comes to publishing is that each calendar is limited to one publishing link.
This is causing many issues that you can't simply revoke a calendar without breaking embedded calendars / having to send out a new public link to people who should still have access.
In order to solve any of the publishing related tickets mentioned above, we first need support for multiple publishing links. Once we have support for that, adding support for more sharing types including "internal busy", "public busy", "public editable", "public busy editable" should be straight forward.
Once we have support for these public types, adding password-protected public shares or shares with expiration-link would also be straight forward.
Overall tasks:
dav_shares
.also cc @raimund-schluessler @skjnldsv
This will require changes to cdav-library
, but i aim at implementing them in a backward-compatible way.
Can cs:publish-url
handle multiple URLs ? We'll have to go with our own thing otherwise.
Can cs:publish-url handle multiple URLs ? We'll have to go with our own thing otherwise.
Not as far as i can tell. We would have to move to our own implementation.
Hi. I suggest to add also a link to issue "Send invitations for shared calendars" #26668 , as it is about shared calendars expected features.
This overview of calendar sharing issues could also reference #5050 issue about sharing from MacOS Calendar.app.
Hi, maybe the "No invites, but invite cancellations sent from shared calendars" #20278 is also a part of this?
That's a bug, not a feature.
I suggest to add #19994 (as mentioned in the this issue, the problem still occurs in our installation, NC Version 26.0.4)
I suggest to add #19994 (as mentioned in the this issue, the problem still occurs in our installation, NC Version 26.0.4)
Seconded: #19994 is still open with NC 27.1.5 and Calendar 4.6.6
This is an overview ticket for feature requests / bugs related to Calendar Sharing:
Sharing
Publishing
Features missing for feature parity with file-sharing: