[nodebb-plugin-beep] NodeBB Censor Curse Words Plugin

shady2k

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:23

What should I do?

<baris>

Apply these changes in the plugin in your node_modules folder until the PR is merged

update to latest nodebb by barisusakli · Pull Request #6 · ninenine/nodebb-plugin-beep

GitHub (github.com)

shady2k

@baris, thank you. Plugin started, but doesn't find any curse words anyway.

<baris>

See my other updates to that same PR
https://github.com/ninenine/nodebb-plugin-beep/pull/6/files

shady2k

@baris, perfect! Thank you very much.

faizanzahid

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?

PitaJ

@faizanzahid open issues on the plugin page on github

faizanzahid

@pitaj @mr_99 thanks! i just opened a new issue.

Allow plugin to work only on topic pages and not on shoutbox ? · Issue #33 · ninenine/nodebb-plugin-beep

Great Plugin indeed. but has some issues. Please see below. Can we have a feature so that I can disallow this plugin on the shoutbox page but let it run for posts and topics only? Also, there is 1 bug in this plugin. When we set the sett...

GitHub (github.com)

faizanzahid

Hi guys,

We urgently need this plugin. Is this plugin compatible with node bb current version?

I remember it used to redirect in infinite loops if a * comes in URL. Has this fixed?

fortunato

Hello!
I am wondering where is the ACP link for this plugin.
I see I can edit the defaultBanList array in the index-js, but for what I am reading here above there should be a Administration link...but where?

Thanks

PitaJ

Should be ACP->Plugins Menu after you install, activate, restart, and rebuild

Cookie

This post is deleted!

Cookie

I am using the latest version of the beep plugin 0.4.2 on the latest version of NodeBB 1.12.2. I have one issue with the beep plugin regarding old topics which were created before I migrated my site to NodeBB which have words which should be censored.

Newly created topics are censored with the beep plugin just fine. In the MongoDB the beep plugin actually saves topics with the censored words, so e.g. "title" : "Ps test censor" or "slug" : "123/ps-test-censor" is persisted in the database. Posts are obviously not modified by the beep plugin in the database but on the fly. Queries on the DB show the full non censored words in all posts be it old or new posts. Old and new posts are correctly censored by the beep plugin on the fly during browsing of NodeBB forum.

To fix this, post processing must be run on all topics in mongodb to modify "title" and "slug" applying the current beep censor rules.
Fortunately, I did not have that many topics to fix, so a quick manual fix is to just open each offending topic once, editing the topic as admin and saving it.

As a future improvement of this plugin, it would be very nice to have a simple button in the admin panel which runs a post-processing script for the above issue. This would be especially helpful on any change of the censor words down the line.

AnOdeToBB

The idea behind this is great but sadly for me it censors parts of words like these below.

Screenshot_2021-05-10 Match Preview County v Dagenham amp; Redbridge(1).png

Screenshot_2021-05-10 County Podcasts.png

is there a fix for this?

many thanks

phenomlab

This post is deleted!

<baris>

I've updated this plugin to work on latest nodebb, and added an illegal usernames setting as well. @nodebb/[email protected]

phenomlab

@baris Can we adjust this plugin so the regex isn't so greedy? By this, I mean a three letter word (considered profane) I want blocked is still detected as being part of "Institute" for example. Another would be "Scunthorpe" but obviously I'm not going to highlight the word I'm looking to block in that one

<baris>

Try with 1.1.2, I noticed a bug in one of the regexes. Not sure if it will fix all the cases but your institute example should work now I think.

phenomlab

@baris thanks very much. I'll check this

the skyfoxx

@phenomlab said in [nodebb-plugin-beep] NodeBB Censor Curse Words Plugin:

@baris Can we adjust this plugin so the regex isn't so greedy?

Maybe more interesting to have a dictionary filter filter instead of regex?

bad-words-next

JavaScript/TypeScript filter and checker for bad words aka profanity. Latest version: 3.0.0, last published: 8 days ago. Start using bad-words-next in your project by running `npm i bad-words-next`. There are 3 other projects in the npm registry using bad-words-next.

npm (www.npmjs.com)

Amazing plugin though