Aurora:
In our community we run many recurring events (support groups, body doubling sessions, regular meetings). Because the participant list for recurring events is not reset, the list quickly becomes inaccurate and continues to grow over time.
I’m not 100% sure what is but it looks like this was indeed the intended behavior for recurring events. @j.jaffeux do you remember the use cases for not reseting “going” participants on recurring events? Like our weekly team calls?
Aurora:
Another problem for us is that the people who create and organize these events (group facilitators) cannot remove participants from the list. Even when we assigned category moderator permissions to them, they still cannot manage the attendee list. Only global moderators or admins seem to be able to remove participants.
Will be fixed by
main ← fix/event-creator-manage-invitees
merged 09:36AM - 31 Mar 26 UTC
Previously, `can_act_on_invitee?` only allowed staff or the invitee themselves t… o update/remove an RSVP. This meant event creators and organizers (e.g. group facilitators with category moderator permissions) could not manage their own event's attendee list — only global moderators or admins could.
This updates the guardian check to also allow users who `can_act_on_discourse_post_event?` (i.e. users in the allowed event groups who can edit the event post) to act on invitees. The redundant `staff?` check is removed since `can_act_on_discourse_post_event?` already checks for staff.
https://meta.discourse.org/t/335780
2 Likes