Postbased content killer [3.6 compatible]
 

We have been using the replacement variable manager and the censorship functions in vBulletin for a long time now, and it works fine as long as our users types the censored words as we have entered them in the managers. Sometimes our users gets smart and instead of typing in "censored word" they type "c e n s o r e d w o r d" and suddenly they have passed through the censoring system. This is very annoying and I still can't find a censorship manager that handles regular expressions.

This is why I wrote this plugin - to handle users that tries to avoid the censoring with different kind of characters, spaces, etc.

The content filter should be used with caution - it kills the content completely (without destroying the original of course), if it finds any matches of a filtered word - just like I wanted it from the start.

Unfortunately I have'nt done any admin interface yet (because I can't), to handle patterns, but this is a good start, and configuration is made from the plugin manager. Filtering can be handled in 3 different ways:

• On match, the post will look empty

• On match, the post will show an errormessage (randomized or static - quite ugly actually)

• On match, posts are replaced with a vbphrase

You can also set usergroups that can see the message unfiltered, and which users (by userid) that will be excepted from the filter.


Details:

• 1 product

• 2 phrases

• 2 plugins (postbit and quote)

Install it by import the product.

*reserved

but i really dont understand it to the fullest... its pretty much replace text? how did u go about doing the code?

It just replaces the $post[message] with another string if any matches are done, so admins/moderators can still see the original post.

why would your message be *reserved ???

The default plugin also affect PM's. To avoid this, add the following code at the top of both content_killer_quote and content_killer_postbit:

I just realized that using return; here is NOT a good option to stop filtering in PM. The reason is that the hook, after returning, is ignored by vBulletin. Soon, there will be a fix for this, and configuration will be moved to anoter place in admincp.

The old "private"-thing has been fixed when I converted this hack to a "admin-configurable" interface.

Tested with 3.6

Coming soon

• Auto softdelete posts that contain a filtered word
• Auto search and replace filtered words instead of filtering whole posts
• Choose admingroups to protect from filtering