반복 이벤트 "going"이 더 이상 삭제되지 않음

안녕하세요,

사용자가 주간 반복 이벤트에 대해 "참여"를 클릭하면, 보통 이벤트가 끝나면 바로 투표가 사라지고 다음 주에 대한 새로운 투표가 항상 표시되었습니다. 그런데 지금은 투표가 계속 쌓여 긴 목록이 만들어지고 있습니다.

이벤트 표시 설정을 변경했을 수도 있지만, 이를 되돌릴 설정을 찾지 못하고 있습니다.

해결 방법이 있을까요? 감사합니다.
Ann

1개의 좋아요

Maybe I need to describe it better:

  • you have a weekly repeated event Monday evening 7-8pm
  • some people have clicked going, interessted or not coming and this is shown by the respective symbol on their listed avatar
  • next Monday at 8:01pm all those symbols are gone, avatars stay listed but greyed out
  • event topic then shows date of the Monday one week later and nobody “going” etc until the first users click again

Now I fiddled around with some visibility setting that the ones attended today are longer visible then 8pm or that the event is not deleted or anything like that…
But now their avatars are never reset and greyed out but all “going” participants are accumulated over weeks and shown as actively “going”
I can’t find the setting to make it the same as before, at 8pm the event is cleared and set to next week without any participants

Any hint where I can revert this?

And yes, I know, document your changes :slight_smile:

Hi Ann — sorry for the delay here, but thanks for reaching out about this! You’re right, this was a recent change to RSVP to the current and future instances of recurring events. We’re discussing this internally to see how we might improve upon this further. I’ll follow up with more information once I have something to share!

2개의 좋아요

Hello @lindsey ,

do you have further information on this topic?
At the moment we are exporting the event to see who changed their state when and then remove them from the list manually.
That’s a bit of a hassle.

Thank you for any update

1개의 좋아요

Hi @anko127 — thank you for following up! I can appreciate how much of a hassle this manual effort has been, and we definitely want to fix that up for you.

Our plan is to improve recurring events to allow people to choose whether they are RSVPing to the single upcoming event, or to every event in the series. We’re finalizing the design work now and then we’ll be getting this worked in front of our engineering team. I don’t have an ETA on when it will be fixed, but it will be in our “next up” projects so I should be back with an update soon.

1개의 좋아요

Any news here? Thank you

Hello @lindsey ,

Do you have any update on this topic?

To Reset the participants list when the Event has passed.

Thank you

I’m afraid I don’t have an update for you, @anko127 — this is still in our backlog but we have not yet prioritized it for development. I’ll discuss with the team to see when we might be able to pick this up.

I think it was working when I startet using Discourse prior autumn 2024, could it just be a misconfigured setting like keeping History for the Event?

1개의 좋아요

We are experiencing exactly the same issue described above.

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. After a few weeks it no longer reflects who is actually attending a specific occurrence of the event.

This creates a lot of confusion for both organizers and participants.

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.

Since we have many groups organizing their own events, it is not practical for admins to manually manage all participant lists.

For communities like ours that rely heavily on recurring events, this makes the RSVP functionality very difficult to use.

Are there any updates or plans to improve how recurring event attendance is handled?

2개의 좋아요

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?

Will be fixed by

https://github.com/discourse/discourse/pull/38966

3개의 좋아요

Because we don’t have per date event entry I think.

Hi there,

Thank you for looking into it.

But this sounds like “ Working as designed, no bug” or are you still investigating how to provide this automatic reset after event expiry?

We would really appreciate this, thank you.

Yeah, it’s unfortunately more work than we can “allocate” on this plugin right now. We need to store each “dates” instead of just storing the “recurrence formula”. It’s planned, but no dates yet.

I’m happy to share that Discourse now supports more granular RSVPs on recurring events. Members can now choose between RSVPing to a single occurrence of the event, or to all future occurrences. You can learn more about this here:

1개의 좋아요

업데이트: 월간 이벤트의 경우 정상 작동하며, 이벤트가 종료된 후 사용자들이 초기화됩니다. 다만, 이벤트가 종료될 때까지는 이벤트 시리즈가 이벤트 캘린더에 표시되며, 첫 번째 이벤트만 확인된 상태에서도 마찬가지입니다.

원래 게시물: 린즈, 죄송하지만 “참석” 사용자의 초기화를 방지하는 숨겨진 옵션이 있어야 하는데, 저는 1년 전 또는 그 이전에 우리 시스템에서 그 버튼을 눌렀을 가능성이 큽니다!

저는 이 새로운 옵션을 이벤트가 지난 후 일회성 참석자들이 초기화되도록 구현했다고 확신합니다. 하지만 우리 시스템에서 테스트해 보니, 이벤트가 종료된 후에도 여전히 작은 체크 표시와 함께 저의 이름이 표시되었습니다:

매일 반복되는 이벤트를 만들고, 13:40에 '참석’을 클릭했는데 작은 체크 표시가 나타났습니다. 그런데 이제 15:38이 되어 종료 시간이 지났음에도 불구하고, 저는 여전히 등록되어 있는 상태로 표시됩니다(내일 이벤트). ‘참석’ 버튼을 다시 클릭하지 않았는데도 말입니다.

더 조사해 보니: 사이드 메뉴의 ‘예정된 이벤트’ 항목에서 '내 이벤트’로 전환하면 모든 반복 이벤트에 등록되어 있는 것으로 표시됩니다(매일 반복되는 이벤트는 파란색, 월간 이벤트는 분홍색). 위 사진에서 보듯이 저는 정말로 다음 발생분(occurrence)에만 등록했습니다.

이 기능이 작동하도록 하려면 활성화/비활성화해야 하는 다른 옵션이 있습니까?

제가 무엇을 망가뜨린 걸까요? 시간대나 언어 설정 문제일 수 있을까요?

흥미롭네요, 공유해 주셔서 감사합니다! 확인해 본 후 다시 연락드리겠습니다.

@anko127 님, 보고해 주셔서 감사합니다 :+1:

실제로 내 이벤트 캘린더에서 다음 이벤트에만 RSVP를 했음에도 불구하고 모든 예정된 이벤트가 표시되는 문제가 있었습니다.

7개의 좋아요

고마워요, 빠르네요!

1개의 좋아요