비스태프 사이트 회원이 주제 초대 생성 허용

기여 기능
1

I’ve had trouble creating an invite with the arrive_at topic enabled as a user.

I can see the Invite button after clicking “Share” on the topic in public sections. But when I create the invite, the “arrive_at” field isn’t set in the database (I checked the topic_invites table with Data Explorer). When I edit the invite later, the “arrive_at” field doesn’t show up and can’t be edited.

I looked for related settings in both admin and group settings and couldn’t find any.

We’re not using must approve users. We have trust_level_2 in Invite allowed groups setting.

Seems like there must be some other setting (or hard-coded) limit to use topic invites.

UPDATE: I think this is a bug actually. I can reproduce this issue here on Meta in this very topic. It’s impossible to create an invite link with arrive at topic set (as a tl2 user, not staff).

2개의 좋아요
Creating and using invites
2

Is the topic in a public or private category? So, is everyone allowed to see it?

3

The topic is public.

For topics not visible to everyone, it looks like the “Invite” button is correctly missing in the “Share Topic” modal.

1개의 좋아요
4

Yes you are right. It’s limited to staff

Sorry for asking whether the topic is public. I just remembered that it mattered in some cases.
For example Rules for inviting people to topics? - #10 by JammyDodger

2개의 좋아요
5

현재 동작은 의도적으로 설계된 것입니다. 하지만 관리자가 아니거나 관리자가 아닌 멤버들이 초대 생성 시 주제를 지정할 수 있도록 하면 유용할 수 있다는 점은 이해할 수 있습니다. 그래서 이 내용을 Contribute > Feature 채널로 전달하여 검토를 요청했습니다.

사람들은 다양한 방식으로 초대 시스템을 설정하길 원합니다. 얼마 전 한 분과 대화했는데, 그분은 기본 주제를 설정하되 멤버들이 이를 변경하지 못하도록 하길 원했습니다.

1개의 좋아요
6

Not trying to argue, but this line in the docs:

suggests otherwise.

That’s why I was suggesting it might be a bug.

2개의 좋아요
7

Hmm.. you’re right! There does seem to be something amiss here. Even as an admin, if I select the Share button on the topic menu and then Invite, the created invitation does not have the topic selected already. I don’t recall if this is by design but it certainly isn’t as intuitive as it could be.

That documentation topic does need an update too, so thanks for flagging that.

2개의 좋아요