How to get notifications on group membership requests?

support
1

Hi,

We have a private category restricted to a group. When a non member tries to read a post in that category, they get offered the option to request membership (as expected)

the group ownes can see the requests to join at /g/[name_of_group]/requests, but they do not receive a notification (either on the site or as email)

This makes it tricky to properly manage the requests, as they get stalled there until one of the owner goes there and grants access.

Is there a way to get notifications in a setting I missed?

2

This sounds like a bug to me… I noticed I was not getting notifications here on plugin author reqs anymore. @vinothkannans can you investigate what is up here?

3 Likes
4

Thanks Sam,

I’m on v2.4.0.beta2 +235

@vinothkannans, I’m not yet familiar with your dev workflow, but happy to create an issue with more info if needed

5

I’m unable to reproduce the issue here (also in try.discourse and in my local).

https://github.com/discourse/discourse/blob/b60b2a342f8a1f2ea7cfa3475d8efb76a2a600a9/app/controllers/groups_controller.rb#L439-L444

Note, as per the above code the notification PM will be created only for the 5 group owners who recently online. I think your group has more than 5 owners.

We have 6 owners.

4 Likes
6

Looking a bit more at my configuration and trying to find something relevant:

I think one of the admin changed the visibility from “Everyone” to “Logged on users”

image

and now the "Allow users to send membership is checked, but disabled
image

When I’m looking at another group (visible only to logged in users)

image

The “allow users to send membership requests” is disabled and unchecked

Could it be the issue? is this expected that you can’t send membership requests to a group that is visible only to logged in users?

2 Likes
7

Yes, the visibility level setting of group is affecting the “membership requests” feature. The “logged on users” option for group visibility setting is added recently. After that, the membership requests feature should be compatible with “logged on users” option too (not just “public”). I will fix that :hammer_and_wrench:

4 Likes
8

https://github.com/discourse/discourse/commit/82c5a1d20fa9215b5a8c1bed83db3444f9c418f6

@xav this should resolve the problem.

4 Likes