Closed (fixed)
Project:
Drupal Commons
Version:
7.x-3.6
Component:
Activity/status streams
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
9 Feb 2013 at 01:10 UTC
Updated:
5 Feb 2014 at 05:20 UTC
Jump to comment: Most recent
Comments
Comment #1
ezra-g commentedThe activity stream node access aspect of this was originally been fixed with #1797462: Enforce node access restrictions on Activity stream entires, but checking the "Commons Activity Streams - Activity (Site-wide) " view shows that the necessary node access filters are not in place.
Comment #2
japerryThe first part of this is fixed in this commit, export the feature with the needed node access filters.
http://drupalcode.org/project/commons_activity_streams.git/commit/9baea2...
Comment #3
japerryVerified second issue is happening. Email gets sent out to regular users:
1) a post is created by themselves (and is published)
2) a comment is created by anyone on their post (published or not)
3) a post is created by admin (and is unpublished)
4) a comment is posted by anyone on unpublished nodes.
I think #1 and #2 is okay, but the other ones are not.
Comment #4
ezra-g commentedI filed #1918666: Entity Access support to see how the Message* maintainers feel about the best approach for implementing node access with Message Subscribe.
Comment #5
ezra-g commentedComment #6
ezra-g commentedThere's now a patch to Message subscribe at #1918666: Entity Access support.
Comment #7
ezra-g commentedI tested with patches to Message and Message Subscribe (referenced below) to implement alterable access control of Message entities, and to support entity_access() in message subscribe.
I tested by having a non-administrative user follow a group, then posted 2 nodes into the group as an admin - one published and one unpublished. Only the message about the published group was sent.
I believe this is fixed.
http://drupalcode.org/project/commons_activity_streams.git/commit/4aea509
http://drupalcode.org/project/commons.git/commit/fd15bed
Comment #9
tanius commentedI believe it's not fully fixed. With the patches from #7 applied, I created a comment on a post in a private OG group, and a test user not in that group but following me got an e-mail notification about it.
Notes:
Comment #10
tanius commentedI think this is not fully fixed yet.
I tested by having a non-administrative user follow another (admin) user who is member of a private group. Then using the latter user to post a comment to a private thread within this private group. An e-mail notification about this went out to the former user, but there was no notification in the activity feed about this. Such a notification i sonly sent when creating comments, but not posts.
Comment #11
tanius commentedIn combination with issues #1978046 and #1966434 this issue currently makes it possible to access all comments of a private group by following the user who created the group, or all users in the group, or the group itself.
As a quick workaround for this privacy implication, I temporarily disabled sending notifications to a user's followers at all. By adding this in
profiles/commons/modules/contrib/message_subscribe/message_subscribe.moduleline 360:Plus, make sure the group has no non-members as its followers. You can also set its creator to "Anonymous", though I think that's no longer needed with the above patch. (Sorry for just having this and not a patch to fix. Still a Drupal beginner ...)
Comment #12
behoppe333 commentedThis is still an issue in Commons 3.3 (and perhaps beyond). See open issue "Blocked user still receives email notifications" https://drupal.org/node/2092441
Comment #13
Leeteq commentedIs this still a problem in the latest release?
Comment #14
flyngo commentedsubscribe
Comment #15
Leeteq commentedThis seems totally unrelated to #2092441: Don't send commons_notify mails to blocked users, and thus unnecessarily re-opened.
Setting back to fixed.