No category notifications for staged users in private category

Staged users on my instance are not getting e-mail notifications for posts in private categories, even if they’ve been added to a group which should give them permission to. This seems to have stopped working with a recent change in Discourse.


:ballet_shoes: Steps to reproduce:

  1. Create a staged user
  1. Create a category which is only visible to a specific group (members can “Create / Reply / See”, but no other permissions assigned)

  2. Add the staged user to the group by entering their e-mail address on the “Bulk Add To Group” button

  • the “Add Members” dialogue box doesn’t recognise the usernames of staged users, probably by design)
  • the user does show up in the member list, though
  1. Go to the staged user’s preferences page, and set them to “Watching” the category

  2. Make a new post in the private category

:white_check_mark: On my community’s dev site (running v2.4.0.beta3 +10) this successfully sends an e-mail notification to the staged user, as well as any non-staged users who are watching the category.

:negative_squared_cross_mark: On our live site, running 2.4.0.beta9, nothing about the post shows up on the user’s notification page. If I then un-stage the user by clicking “Impersonate” on the admin page for their user, notifications start coming through fine.


:wrench: The two sites have almost-identical configurations (SSO is enabled on both).


:art: Background

Our use-case is that we’re migrating mailing lists onto Discourse, but the lists are for private sub-groups of our community (hence the category which is visible only to members of a specific group) – and we’d like to support staged users for people who’d prefer to continue interacting via e-mail, so it’s a simpler transition from the existing lists.

The easiest way we’ve found for people to continue getting all messages sent to the mailing list by default (one of the main benefits of switching to Discourse will be being able to dial down the level of e-mails without leaving the list entirely, so it seems fair to start with the existing behaviour of receiving everything) is to use Mozilla’s group-category-notification plug-in to have all members of the group “Watching” the category.

I’ve read that being able to add staged users to groups “could stop working at any time”, so I’m open to other ideas :pray:

1 Like

We recently added a fix because staged users were receiving notifications for content they shouldn’t have been able to see:

@Roman_Rizzi still, if the user has access to the group it should work right?

5 Likes

@eviltrout thanks, that looks like exactly the problem:

# lib/guardian/topic_guardian.rb, L152
-    can_see_category?(topic.category)
+    category = topic.category
+    can_see_category?(category) &&
+       (!category.read_restricted || !is_staged? || topic.user == user)

The logic has changed from checking if can_see_category?(topic.category) passes (which I think it does, as per below), to disallowing the notification if the user is staged in all cases.

This seems like a bug? :bug: Otherwise staged users will never be sent notifications for posts in private categories, even if they’ve explicitly been granted permission to. Should I move to #bug?

can_see_category?

I think can_see_category? is passing, because of the last line:

def can_see_category?(category)
    return false unless category
    return true if is_admin?
    return true if !category.read_restricted
    return true if is_staged? && category.email_in.present? && category.email_in_allow_strangers
    # this one:
    secure_category_ids.include?(category.id)
  end
  • the user is staged
  • the category has an “email in” address set
  • catgeory.email_in_allow_strangers is enabled) I disabled email_in_allow_strangers because I realised I don’t need it… but secure_category_ids.include?(category.id) returns true
1 Like

I submitted a pull request which restores notifications to staged users:

EDIT: merged! Thanks y’all

6 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.