-
Notifications
You must be signed in to change notification settings - Fork 244
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
Incorrect handling of CLASS:PRIVATE Flag from iCal import #4876
Comments
\OCA\DAV\CalDAV\Calendar::getChild does check for the classification but it might be buggy. Unfortunately I'm very pressed for time at the moment, but if you're up for it, you could step through it with your debugger to see where the error happens. Otherwise it will take some time until we get to it. Specification is here: https://www.rfc-editor.org/rfc/rfc5545#section-3.8.1.3 |
Thats unfortunately beyond my skill set, but as a quick fix, i think NC Calendar should rather ignore the CLASS:PRIVATE field than hide the appointment from the owner but show it to everyone else ;) |
Can you have user B export the event from their side and check if the file still contains |
I exported the appointment from User B's NC Web GUI and it keeps the CLASS:PRIVATE flag |
Here is an anonymized version of the original iCal file from doctolib |
In #4044 it is discussed how to handle private events. |
Steps to reproduce
Related forum post: https://help.nextcloud.com/t/rendez-vous-not-visible-in-shared-calendar/71432
Expected behavior
I dont know what the expected behaviour of iCal Files that contain a CLASS:PRIVATE Flag is, but i am pretty sure that a imported appointment should show up for the user that created it and synced it using his/her credentials (USER A) - it should maybe not show up for USER B if thats the intended purpose of CLASS:PRIVATE, not showing an appointment to users with shared access to the calendar.
Actual behaviour
An appointment that was created and synced by USER A is not visible to USER A. neither in the Web-GUI nor in a syncecd Android calendar, it shows up on USER B's iOS Calendar (iphone) and in USER B's NC Web Calendar View. So pretty much the opposite of what you would expect to happen.
Calendar app version
4.2.0
CalDAV-clients used
Davx5 / aCalendar (Android), emClient (Windows 10), iOS Calendar (iPhone)
Browser
Chrome 108.0.5359.125
Client operating system
Windows 10
Server operating system
Debian Bullseye / Docker
Web server
Other
Database engine version
Other
PHP engine version
Other
Nextcloud version
25.0.2
Updated from an older installed version or fresh install
Updated from an older version
List of activated apps
Nextcloud configuration
Web server error log
No response
Log file
No response
Browser log
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: