Bug #2686
closedReplying to Group Announcements
100%
Description
I'm receiving forwarded messages from people who are replying to group announcements via email. I didn't think this was possible and just tested -- it isn't. It looks like you can't even reply to group announcements when you are logged into the Commons (I thought you used to be able to do that). That being said, our documentation says otherwise:
- http://news.commons.gc.cuny.edu/2012/08/15/commons-1-4-reply-by-email/
- http://help.commons.gc.cuny.edu/faq/#How_do_I_reply_to_email_notifications.3F.C2.A0
I'm not sure if announcements were originally set up for users to reply by email and directly through the group or if perhaps something changed along the way. I'd be happy to update the post/FAQ above, but first just want to clarify what is supposed to happen.
Files
Related issues
Updated by Raymond Hoh over 11 years ago
Part of the problem of why the commons@gc.cuny.edu address is receiving a bunch of replies is related to #2685.
As for being able to reply to group announcements via email, this has always been the case. However, if we are stringent that group announcements shouldn't be replied to, we do need to fix this.
It also does sound like RBE should check the activity comment status before manipulating the email headers. So this is a legitimate bug for RBE.
Thanks for reporting, Sarah!
Updated by Sarah Morgano over 11 years ago
- File noreply.jpg noreply.jpg added
Wait, now I'm super confused! Are users supposed to be able to RBE to group announcements? Because right now they can't. They also can't reply when they are logged in to the group (screenshot attached).
Updated by Matt Gold over 11 years ago
- Category name set to BuddyPress (misc)
- Status changed from New to Assigned
- Assignee set to Boone Gorges
Updated by Raymond Hoh over 11 years ago
Just going to quote myself from my previous comment:
As for being able to reply to group announcements via email this has always been the case.
Users can't reply to group announcements on the website, but it's technically feasible for a user to reply to one via email if the user is subscribed to the "All Mail" option in the Group Email Subscription plugin. A group announcement is technically just a group status update so if a user is subscribed to "All Mail", RBE will kick in and manipulate the email.
Updated by Sarah Morgano over 11 years ago
Thanks for clearing that up for me, Ray. I think I was mostly confused by the fact that you could RBE, but not when you're logged in to the site.
Updated by Boone Gorges about 11 years ago
What do we want to be the case? It seems to me that, since we block activity comments on group announcements through the UI, we should also block RBE for this activity type as well. Ray, is that something we can easily do?
Updated by Matt Gold about 11 years ago
Boone Gorges wrote:
What do we want to be the case? It seems to me that, since we block activity comments on group announcements through the UI, we should also block RBE for this activity type as well.
Agreed
Updated by Sarah Morgano about 11 years ago
Do you think we might be limiting group conversation by not having this feature through the UI? I'm not sure if it was decided at a certain point for members not to be able to reply to group announcements to keep conversations in the forums, but at one point we did allow this and IMO it makes sense to members to reply to announcements from group admins. That being said, I'm totally open to what the group wants.
Updated by Matt Gold about 11 years ago
the problem is that you then have conversations taking place in the activity stream and in the forum, which can be confusing -- people can remember that they replied to something but not where they did. I think our strategy is to channel everything to the forums. I hear you, though, that it's not a perfect solution, but I'm not sure that there is one here.
Updated by Raymond Hoh about 11 years ago
I just looked into this issue a bit more and it appears as though CAC has some custom code that disables commenting on group announcements.
In actuality, there are two Group Announcement plugins:
- The one used on CAC - there is custom code in the activity entry template that restricts group members from replying using a customized permissions function -
cac_activity_can_comment()
. This function shouldn't be used in the template, but rather we should hook onto the'bp_activity_can_comment'
filter instead - The one available on CBOX - we do not restrict group members from commenting on group announcements
For the purposes of this ticket, I will do the recommendation I set out in point 1 and patch up RBE to check the activity comment status with bp_activity_can_comment()
.
However, what should we do for the group announcements plugin bundled with CBOX? Should we also restrict replies there as well?
Updated by Boone Gorges about 11 years ago
Thanks for digging deeper, Ray.
Your course of action for CAC sounds good. As for cbox, I think that since that functionality is meant to parallel the Commons, we should do the same there too.
Updated by Boone Gorges about 11 years ago
- Target version changed from 135 to 1.5.1
Updated by Boone Gorges about 11 years ago
- Assignee changed from Boone Gorges to Raymond Hoh
Updated by Boone Gorges about 11 years ago
- Target version changed from 1.5.1 to 1.5.2
Updated by Boone Gorges about 11 years ago
- Target version changed from 1.5.2 to 1.5.3
Updated by Boone Gorges about 11 years ago
- Target version changed from 1.5.3 to 1.5.4
Updated by Boone Gorges about 11 years ago
- Target version changed from 1.5.4 to 1.5.5
Updated by Boone Gorges about 11 years ago
- Target version changed from 1.5.5 to 1.5.6
Updated by Boone Gorges about 11 years ago
- Target version changed from 1.5.6 to 1.5.7
Updated by Boone Gorges about 11 years ago
- Target version changed from 1.5.7 to 1.5.8
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.8 to 1.5.9
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.9 to 1.5.10
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.10 to 1.5.11
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.11 to 1.5.12
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.12 to 1.5.13
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.13 to 1.5.14
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.14 to 1.5.15
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.15 to 1.5.16
Updated by Boone Gorges almost 11 years ago
- Target version changed from 1.5.16 to 1.5.17
Updated by Boone Gorges over 10 years ago
- Target version changed from 1.5.17 to 1.6
Updated by Boone Gorges over 10 years ago
- Target version changed from 1.6 to 1.7
Updated by Raymond Hoh about 10 years ago
- % Done changed from 0 to 100
Boone, for 1.7.x, I've made the decision to remove the older cac-group-announcements
plugin in favor of the one created for CBOX.
- b10ac07 - Brings back
bp_activity_can_comment
for use in bp-nelo - dd72f9a - Adds the BP Group Announcements plugin
I haven't removed the older cac-group-announcements
plugin yet, but it should be deactivated for 1.7 and later removed for 1.7.1.
Updated by Boone Gorges about 10 years ago
Awesome, thanks, Ray!
Can you say a little more about this? I assume that the important bit related to the above is bpga_can_post_group_announcements(). Is that new here, or does that exist in the cbox plugin? Just want to be clear how the problem is being solved here, and whether it needs to trickle elsewhere too.
Updated by Raymond Hoh about 10 years ago
bpga_can_post_group_announcements()
already exists in the BP Group Announcements plugin.
The main decision for removing cac-group-announcements
in favor of bp-group-announcements
was to centralize the group announcement code into one place on CAC. Previously, I didn't know we had another group announcement plugin and had to do some backtracing to find out about cac-group-announcements
.
Also, bp-group-announcements
has more recent updates to it.
Updated by Boone Gorges about 10 years ago
- Status changed from Assigned to Resolved
Awesome. It sounds like this is done, then. Thanks, Ray.