-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: MKCALENDAR without supported-calendar-component-set doesn't support journals by default #45709
Comments
Thank you 👍 server/apps/dav/lib/CalDAV/CalDavBackend.php Line 757 in b769dc4
Sabre also uses "VEVENT,VTODO" as default: https://github.com/sabre-io/dav/blame/7a736b73bea7040a7b6535fd92ff6de9981e5190/lib/CalDAV/Backend/PDO.php#L242 I don't know if that means something would be missing to support it properly, or just an oversight. |
Related: nextcloud/calendar#4436 |
I think it is just an oversight and our backend should be able to handle VJOURNALs just fine. It is probably not included in our code because there is no "official" frontend to render VJOURNALs. |
Bug description
When sending a MKCALENDAR request without
supported-calendar-component-set
, Nextcloud creates a collection that reports to supportVEVENT
andVTODO
, but notVJOURNAL
.However, it is possible to create a collection that supports all three component types, because it works when it's explicitly requested.
Steps to reproduce
supported-calendar-component-set
).supported-calendar-component-set
.supported-calendar-component-set
contains onlyVEVENT
andVTODO
(but notVJOURNAL
).To verify that it's possible to create collections that contain
VEVENT
,VTODO
andVJOURNAL
:supported-calendar-component-set
=(VEVENT,VTODO,VJOURNAL
).supported-calendar-component-set
.supported-calendar-component-set
containsVEVENT
,VTODO
andVJOURNAL
.Expected behavior
The CalDAV RFC says:
So collections that are created without
supported-calendar-component-set
should also support journals.Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: