Restrict users to post certain words per category

[rajput7707 (Prashant Rajput)]

Is there any way to restrict users to post anything containing specified inappropriate words in a specific category only.
Ex. We have set up two categories A and B. Now we want to restrict the users to post anything containing “xyz” (example). in category A only although users should be able to post anything in Category B…

[merefield (Robert)]

Believe this may be global. You might need to create a plugin to “excuse” certain categories.

Watched Words Reference Guide

Looking for information about Watched Words? You’re in the right place! This is a reference guide for describing how the Watched Words page functions and the different types of action types you can use to block specific words on a Discourse site. Watched Words You can setup Watched Words to take actions based on words found in a topic or post (located at .../admin/customize/watched_words ). [image] There’s a max of 2000 words per type of action. On all actions, * can be used …

[Lhc_fl (Linca)]

Can this official plugin help you?

Discourse Automation

This plugin is now bundled with Discourse core. There is no need to install the plugin separately. Summary Discourse Automation lets you automate actions through scripts and triggers. Customisation is made through an automatically generated UI. Repository Link https://github.com/discourse/discourse-automation Install Guide How to install plugins in Discourse [Capture d’écran 2021-07-02 à 15.13.57] Features Easy autom…

Flag post on Words: flag a topic on creation/edition if it contains specific words

[rajput7707 (Prashant Rajput)]

Thanks @Lhc_fl , Since i am new to discourse so unable to understand how to create custom plugin or add our feature into any existing plugin. So could you please elaborate on that how exactly i can get my issue resolved.

[mattdm (Matthew Miller)]

Related feature request: Watched Words tagging — enable by category?

[Canapin (Coin-coin le Canapin)]

Here’s how to add a plugin to Discourse:

Install plugins on a self-hosted site

This guide assumes that you have a self-hosted standard installation. We only support the standard method of install here, so these instructions assume you have a standard install. This guide only applies to self-hosted Discourse instances. If you are using a managed hosting service, the available plugins are controlled by your hosting provider. For example, on our hosting these specific plugins are available by hosting tier. In this tutorial, we’ll install the Discours…

Here’s an example of an automated task with this plugin:

It will automatically flag a post that contains some words in a specific category.
The post’s content will be hidden, but anyone, even regular users, can click a button to show the hidden content.

This can be circumvented with a CSS solution:

The persistence of posts hidden by flags are a bane to our community

Turns out this does create some side effects: When the most recent post in a topic is hidden and a user clicks on the most recent post indicator in the topics list it will try to go to the hidden post but then “bounce” randomly way back higher in the thread. The owner of the hidden post won’t have a chance to edit it because the controls for the post are also hidden. So this appears to be a better solution: body:not(.staff) { .post-hidden a.expand-hidden { display: none; } …

But note his behavior (hidden message can be read by anyone) is discussed, have a look at:

The persistence of posts hidden by flags are a bane to our community

How would you feel about having these auto-hidden-due-to-threshold posts hidden to non-moderators and non-flaggers? (leaving it visible as stubs to people who originally flagged and mods) Keep in mind that this is meant to be a temporary state, people can recover from auto hide by correcting a post.