Basically, we routinely publish a post that should be in hundreds of groups. Because of this, the Recent activity in this group box becomes extremely large.

While researching how this is created, I found there is a message commons_activity_streams_node_created configured for this. I also noticed it uses a token of [commons-groups:in-groups-text].

Is there a list anywhere of commons tokens that can be used?

Comments

ezra-g’s picture

There is not, but this seems worth documenting.

Could you share more about your use case that calls for posting into hundreds of groups?

The expectation with group-based sites is typically that content is either only relevant to a handful of groups or relevant sitewide, in which case it can be posted outside of a group.

Anonymous’s picture

We have created a group for every dept, store, district, region and etc. For instance...

Region 1
- District 1
- - Store 1
- - Store 2
- District 2
- - Store 3
- - Store 4
Region 2
- District 3
- - Store 5
- - Store 6
- District 4
- - Store 7
- - Store 8

We will post a communication (custom Content Type) that we need to display in all or some of the Regions, Districts and/or Stores as it will be relevant to multiple groups. Since there is not a hierarchical structure of groups, we have to select each group the communication will affect. (It would be easier if we could select the top most level and all child levels would get the communication in its group).

For instance...We will send out a communication that a process has changed for all stores in Districts 1 and 4. So, we want this communication to display in the group stream for each of these groups, as well as the individual's stream if they are a member of, or follow, that group.

Does that make sense?

Anonymous’s picture

FYI - For now, I have changed the message to not include the groups.

lsolesen’s picture

Issue summary: View changes
Status: Active » Fixed

Closing old issues. Please enlighten the community if you solved your question or reopen if it is still a problem.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.