In a UX-focused discussion about standalone events in Discourse’s calendar system, tkforbes reported that after an upgrade, standalone events incorrectly display “0 going,” which may mislead users since attendance can’t be indicated for such events. sam agreed it’s a UX issue and tagged jordan.vidrine, who confirmed it was an oversight and submitted a fix PR #672 to remove the “0 Going” label. After the fix, tkforbes noted a related issue: the “Show participants” option still appears in the event’s ... menu, leading to an empty participation page — inappropriate for standalone events. jordan.vidrine acknowledged this and submitted a second PR #679 to hide “Show participants” even for moderators and admins. tkforbes confirmed the behavior was previously visible only to staff, and jordan.vidrine confirmed the fix now applies universally. sam closed the thread, inviting reopen if needed. The issue was resolved through two targeted PRs improving clarity and usability for standalone events.
Upgraded this morning. Have noticed this in my Events today…
I create Standalone events. There is no need for people to indicate their attendance, and in the past “going” was not reported for this event type.
As shown here, “0 going” is shown today. I think this gives a negative impression; people planning to go might believe no one is going! Since it is impossible for people to indicate intentions, I believe “going” should not be reported at all.
It feels UX to me, but agree completely, alerting @jordan.vidrine he worked on redesigning this control, we should be able to handle this edge case easily.
