Selecting the "everyone" group in the allowed_on_groups setting does not enable event creation

The discourse post event allowed on groups setting drop down gives the “everyone” group as one of its options. When selected, the expectation is that everyone will be allowed to create events, but this is not the case. To allow any user on the forum to create an event, the trust_level_0 group would need to be selected.

I think that similar issues with the “everyone” group being included in settings dropdown menues has come up in the past. Probably the setting is just pulling in all groups, but the “everyone” group isn’t a real group and should be excluded from most of these settings.

5개의 좋아요

yea I believe it’s using a list_type: group to pull existing groups - I do this on some of my theme components. In general, I think the everyone group is a bit odd (and not really a group, per se), and TBH, I would rather have an Anon group (or non TL0 and up) to be able to target in various places (or at least as an additional default group). I know in CSS, one can use .anon, but it’s not the same as a group.

5개의 좋아요

이러한 문제가 몇 번 발생했으며, 현재 Templates와 관련된 Contribute > Bug 이슈도 있습니다 - "everyone" group unable to see private templates

이 가상 그룹(pseudo-group)이 모든 기능에서 정확히 어디에 사용되는지 제대로 살펴보고, 일관되게 작동하도록 하거나 드롭다운 메뉴에서 완전히 제거하는 방안을 검토할 것 같습니다. :crossed_fingers:

5개의 좋아요

ran into this one myself today, everyone still doesn’t work but TL0 does

5개의 좋아요

저도 오늘 이 문제를 겪었습니다. 정말 버그입니다! Contribute > Bug 채널로 옮기려 해보겠습니다 (성공).

이 문제를 발견한 유일한 방법은, 유독 끈기 있는 사용자가 건설적으로 불만을 제기한 것이었습니다. 그래서 지난 2년간 저와 다른 관리자만이 이벤트를 게시했던 것입니다!!!

4개의 좋아요

This has cropped up again:

I think that this will trip up most people who use this plugin, unless they know that little trick about “everyone”; perhaps simply hiding the “everyone” option from the options would be a quick way to fix this.

6개의 좋아요