Support #5877

Group Sites -> Activity Stream Limits

Added by Luke Waltzer about 5 years ago. Updated about 5 years ago.

Priority name:
Category name:
Group Blogs
Target version:
Start date:
Due date:
% Done:


Estimated time:


I wonder if it might be desirable to, by default, limit the appearance of group activity items from affiliated Group Sites only to new posts published and new comments posted.

What prompted this was that I implemented a new category on the TLC site and tagged some earlier posts, which, unbeknownst to me, generated an activity item on the TLC group. This activity item then showed up in sitewide activity elsewhere on the site, and prompted both members of the CAC team and other GC staff to tweet out links to fellowship opportunities published earlier in the year, but long since closed. Ideally those folks would have checked the deadline in the posts, but I don't see a rationale for minor (or even major) edits to an already published post flowing over to the group activity (especially with no way to opt out).


Related issues

Related to CUNY Academic Commons - Bug #2564: Editing blog posts connected to groups creates activity item/notificationResolved2013-05-06

Related to CUNY Academic Commons - Bug #2958: Commons Erroneous New Post AlertRejected2014-01-12


#1 Updated by Matt Gold about 5 years ago

I agree that the situation you describe -- tagging old posts with new categories -- should not trigger group activity items and corresponding emails.


#2 Updated by Boone Gorges about 5 years ago

  • Category name set to Group Blogs
  • Assignee changed from Boone Gorges to Raymond Hoh
  • Target version set to 1.10

Ray, can you have a look, referencing #2564? Let's ensure that no notifications are sent for updated activity items.

#3 Updated by Raymond Hoh about 5 years ago

  • Status changed from New to Resolved

This should now be fixed.

We originally implemented the ability to block groupblog edits from creating activity items (and consequently email notifications) in #2844, but somewhere between now and then, we turned this functionality off.

So I've re-enabled it again in commit 6b282e3.

This is available for testing in the new cdev environment.

Also available in: Atom PDF