[buddypress-trac] [BuddyPress] #4285: Not all correct information showing up in Activity Streams

[buddypress-trac at lists.automattic.com]

#4285: Not all correct information showing up in Activity Streams
--------------------------+----------------------
 Reporter:  nickharambee  |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Core          |     Version:  1.5.6
 Severity:  major         |  Resolution:  invalid
 Keywords:                |
--------------------------+----------------------
Changes (by boonebgorges):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Thanks for the additional details, nickharambee.

 > Is there a way of getting forum posts made when the group was private to
 show in 'All Members' tab now that it is public?

 No, there is nothing built into BP that does this. We definitely would not
 want this to be the default behavior - content produced under the
 expectation of privacy should not, by default, be made public at any
 point. A plugin could be written to do what you're asking. It would be
 pretty straightforward - just a matter of flipping hide_sitewide for all
 the group's items from 1 to 0. See #3463 and #3857.

 > Perhaps this is a bug in GTM and I should add a support ticket on their
 plugin page?

 It's probably the case that GTM marks its activity items as hide_sitewide
 = 1. Whether this is a bug or a feature depends on your point of view, but
 yes, I would encourage you to talk to the dev about it.

 > I would like all of my users to be able to see all of the activity, but
 only members to be able to edit and post items, so I don't really want my
 groups to be public groups

 As I alluded to on the other ticket, I think you *do* want to make the
 groups public, and then put a customization in place that keeps non-
 members from joining the groups, or from posting content. This could be
 done with about three simple template hacks. (It could probably also be
 built into a plugin, but it would be a lot trickier.)

 It sounds like the behavior you've described is not due to a bug in BP
 (aside from perhaps the shortcomings described in other tickets), so I'm
 going to close it.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4285#comment:3>
BuddyPress <http://buddypress.org/>
BuddyPress