[nodebb-plugin-beep] NodeBB Censor Curse Words Plugin
-
@Ted am not quite sure, I have removed and reinstalled the plugin on my site and it's working okay for me.
Could you walk me through how you installed it?
Can you see the nodebb-plugin-beep folder in the node_modules folder of your nodebb installation ? -
Up and running successfully - my server decided to be silly.
The plugin works using a predefined list of curse words. Perhaps in future revisions the admins could add words to this, and users could decide whether or not they even want their language to be censored.
Everything seems to function great. It even censors titles. The only slight glitch I've found is that if a "curse word" is posted with some sort of capitalization, the censorship process removes the caps.
All in all, it's pretty neat and solid, with plenty of uses beyond keeping potty-mouths in check.
-
@Ted Nice. Thanks for the feedback.
I will look for a workaround. Am also working on an admin settings interface.
If you want to change the list of banned words you would have to open the index.js file and edit the array. -
awesome!
this is going to be epic once you get the ACP interface going too 
-
@psychobunny @Ted Added the APC interface, you can change the words you want to ban now.
You can update with :
npm install nodebb-plugin-beep -
Thanks for the feedback guys. I have pushed much prettier version to npm, I thought my code was broken till I realized a greasemonkey script was not playing nice with the client side script.
@Ted the case of the words will be maintained and not be converted to lower case.
Also, please note that urls will also be censored, which means they will most probably 404.
-
@Hưng-Thành-Nguyễn Should be fixed now
-
A possible expansion of this plugin would be to potentially reject posts containing certain words. Not that you'd be looking to block posts of those who curse, but if you were having spammers manually register and post a similar message, you could use a string from that message to prevent it from being posted.
-
Is there any way that you can customize the curse word output?
like: NodeBB --> NödeBB
-
@Ted said:
A possible expansion of this plugin would be to potentially reject posts containing certain words. Not that you'd be looking to block posts of those who curse, but if you were having spammers manually register and post a similar message, you could use a string from that message to prevent it from being posted.
Yeah, +1 for this
That would be an awesome spam blocker plugin -
I have this error:
8/2 22:32 [29610] - ^[[31merror^[[39m: TypeError: Cannot read property 'buildHeader' of undefined
at Object.Beep.init [as method] (/opt/nodebb/node_modules/nodebb-plugin-beep/index.js:17:54)
at /opt/nodebb/src/plugins.js:460:13
at /opt/nodebb/node_modules/async/lib/async.js:125:13
at Array.forEach (native)
at _each (/opt/nodebb/node_modules/async/lib/async.js:46:24)
at Object.async.each (/opt/nodebb/node_modules/async/lib/async.js:124:9)
at fireStaticHook (/opt/nodebb/src/plugins.js:450:9)
at Object.Plugins.fireHook (/opt/nodebb/src/plugins.js:406:5)
at Plugins.reloadRoutes (/opt/nodebb/src/plugins.js:129:11)
at /opt/nodebb/node_modules/async/lib/async.js:656:23
TypeError: Cannot read property 'buildHeader' of undefined
at Object.Beep.init [as method] (/opt/nodebb/node_modules/nodebb-plugin-beep/index.js:17:54)
at /opt/nodebb/src/plugins.js:460:13
at /opt/nodebb/node_modules/async/lib/async.js:125:13
at Array.forEach (native)
at _each (/opt/nodebb/node_modules/async/lib/async.js:46:24)
at Object.async.each (/opt/nodebb/node_modules/async/lib/async.js:124:9)
at fireStaticHook (/opt/nodebb/src/plugins.js:450:9)
at Object.Plugins.fireHook (/opt/nodebb/src/plugins.js:406:5)
at Plugins.reloadRoutes (/opt/nodebb/src/plugins.js:129:11)
at /opt/nodebb/node_modules/async/lib/async.js:656:23What should I do?
-
Can we have a feature so that I can disallow this plugin on the shoutbox page but let it run for posts and topics ?
Also, there is 1 bug in this plugin. When we set the settings to Asterisk, then if a person makes a post using a banned word let's say s e x. then the topic URL also gets * which makes the URL request into re-direction loop and we can then never access that topic via URL.
Another bug is that it does not filters words in topic title, i.e it does not say "You cannot use 'BANNED word' in topic title" as it says in topic posts. It lets the user post with a ban word.
When are you guys going to release an update?
