[buddypress-trac] [BuddyPress] #2005: [patch] e-mail notification for group invites

[buddypress-trac at lists.automattic.com]

#2005: [patch] e-mail notification for group invites
--------------------------------------+-------------------------------------
 Reporter:  bi0xid                    |       Owner:     
     Type:  enhancement               |      Status:  new
 Priority:  minor                     |   Milestone:  1.3
Component:  Core                      |     Version:     
 Keywords:  group notification admin  |  
--------------------------------------+-------------------------------------

Comment(by boonebgorges):

 I assume that the OP's issue is that it's possible for A to send an
 invitation to another member B to join a private group, even though A is
 not an admin or a mod of that group, so that B is unable to accept the
 invitation.

 If so, that seems like a bug. Either non-admin-mods should not be able to
 send invites to private groups, or they should be fully function
 invitations.

 Regardless, I'm not able to reproduce it on the latest trunk. I am unable
 to send an invitation to a private group as a non-admin. I can get to the
 Send Invites page, and I can see a list of my friends in the left-hand
 checkbox list, but when I check one of them, the AJAX that creates the
 invite and puts the friend on the list on the right-hand side of the page
 fails, so the real invitation never gets sent. This also seems like a bug.

 So there is a larger question about how BP should handle invitations to
 private/hidden groups. My feeling is that one of two things should happen:
 1) There should be a switch in the group admin area that allows admins to
 choose whether non-admin-mods can invite others to the group. If set to
 No, then non-admin-mods will not see Send Invites at all.
 2) We allow all members of private groups to send invitations. If people
 want to control who can and can't send group invites, they can use a
 plugin like http://wordpress.org/extend/plugins/invite-anyone/

 I think that (1) is a reasonable solution, though it takes a bit more
 work. I'd be interested to hear feedback on that idea.

-- 
Ticket URL: <https://trac.buddypress.org/ticket/2005#comment:2>
BuddyPress <http://buddypress.org/>
BuddyPress