- Issue created by @NickPeeters
- π³π±Netherlands NickPeeters
I already found a workaround that works for me. I disabled the requirements & permissions lines in "google_calendar_service.routing.yml" under "google_calendar_service.view_events:" (on line 37 & 38), because in my case everybody is allowed to see the events, I think this shouldn't cause any problems (only when I update the module it will be overwritten). After that I (or rather ChatGPT) made some changes in "CalendarEventAccessControlHandler.php" to make it work. Maybe not the best solution, but it works :)
- Assigned to danrod
- Merge request !9Issue # 3412561 by danrod: Misc fixes for the permission issues reported in issue 3412561 β (Merged) created by danrod
- Status changed to RTBC
about 1 year ago 5:55pm 8 January 2024 - π¨π¦Canada danrod Ottawa
I reviewed this and there were some permissions used at
google_calendar_service.routing.yml
,src/CalendarAccessControlHandler.php
, andsrc/CalendarEventAccessControlHandler.php
which were not defined atgoogle_calendar_service.permissions.yml
, I changed these and permissions seem to work now, I created a new MR for this, please review. - Status changed to Needs review
about 1 year ago 6:02pm 8 January 2024 - π¨π¦Canada danrod Ottawa
Some screens of the permissions working fine:
Authenticated users with permissions to add/edit/delete event entities:
Anon users with permissions to view the event entities:
- Issue was unassigned.
- Status changed to RTBC
about 1 year ago 3:47pm 10 January 2024 - Status changed to Fixed
about 1 year ago 4:18pm 10 January 2024 Automatically closed - issue fixed for 2 weeks with no activity.