Bug #14223
closed
Non-public site visibility change should update all related site activity visibility to hidden
Added by Raymond Hoh about 3 years ago.
Updated over 2 years ago.
Category name:
BuddyPress (misc)
Description
If a Commons site changes their site visibility from public to a non-public option (under "Settings > Reading" in the admin dashboard), we should update all related activity data for blog posts and comments so they are hidden sitewide as well.
Should also write a script to handle existing blog activity to see which ones might need to be hidden. This might take awhile to run. A quick count query for blog post activity across all subdomain sites is ~65,000. For blog comments, that number is ~39,000.
Related: #14209.
- Target version changed from 1.18.8 to 1.18.9
- Target version changed from 1.18.9 to 1.18.10
- Target version changed from 1.18.10 to 1.18.11
- Target version changed from 1.18.11 to 1.18.12
- Target version changed from 1.18.12 to 1.18.13
- Target version changed from 1.18.13 to 1.18.14
- Target version changed from 1.18.14 to 1.18.15
- Target version changed from 1.18.15 to 1.18.16
- Target version changed from 1.18.16 to 1.18.17
- Target version changed from 1.18.17 to 1.18.18
- Target version changed from 1.18.18 to 1.18.19
- Status changed from New to Staged for Production Release
- Status changed from Staged for Production Release to Resolved
Just ran the CLI script to switch existing public blog activity items that needed to be hidden.
The numbers are interesting. Roughly 40% of the public blog post activity needed to be switched to hidden and 50% of public blog comment activity needed to be switched to be hidden.
An assumption can be made that once a public site's main purpose or goal is completed, the site's privacy setting usually switches to a private visibility setting afterwards.
Thanks for this work and analysis, Ray. Interesting indeed. That's a lot of content moving to private. I wouldn't have thought that so many would change settings later in a site's life, but because it's privacy and largely an academic setting our users may be more vigilant on that front. I'm adding a couple more watchers here as an FYI.
really interesting data point!
- Related to Bug #15134: Broken site image/icon added
Also available in: Atom
PDF