We have a self-hosted Discourse running on the latest.
In the past, posts that were hidden due to multiple user flags or due to a Moderator agreeing with a user flag were still visible to users if they hit the “Show hidden content” button.
Now, however, it seems users can no longer do that. A hidden post is inaccessible.
When did this change in behavior go in?
Is there a setting we can use to control this behavior?
It is very important in our community that the content, though hidden, be accessible to those who want to see it.
2 Likes
Lilly
May 24, 2023, 2:48pm
2
i think this has been changed not long ago, and is no longer possible by regular users. by default only staff can view the posts hidden by flags now.
4 Likes
Canapin
(Coin-coin le Canapin)
May 24, 2023, 2:55pm
3
Indeed. The related discussion is here:
Community moderation is great – if enough people flag a post to hide it, moderators don’t need to get involved. What’s better is that the user who made the post is given an opportunity to improve the post so that it abides by the rules. But what if the user opts not to improve the post, and just lets it sit? The post remains “hidden” for all eternity.
In this perpetual state of being hidden, the post continues to waste a bunch of space on the thread, as it is as large as a normal post:
[image…
4 Likes
Lilly
May 24, 2023, 2:56pm
4
yea i was searching for that topic. here is the particular post about how it works now:
As of this change we have changed the behaviour as described by @mcwumbly above, and regular users (including the flaggers themselves) will no longer be able to expand the ignored content. This is the new baseline behaviour, and doesn’t require any additional setup.
We didn’t include the ability to configure whether TL4 users should be able to as part of this change to keep the scope manageable. By default TL4 users can still expand the hidden content.
4 Likes
I had created a bug report a while ago on this:
So when you react to a flagged post, it causes the following to happen:
I also have a direct explanation on this:
Thanks, all, for the replies and details. Looks like this change went into the latest update.
As it turns out, it’s a serious and problematic change for a Discourse in an organization I’m part of.
I’ll continue in that Topic.
3 Likes