badwords list per user
 

To censor or not to censor, that is the question.

The answer, so far, has been not to because I see it as a restriction of freedom of speech.

However, if individual users had the ability to manage their own personal badwords list, then it is self-censorship based on an individuals own sense of what is acceptable or not.

1. Create a new custom Profile Field
2. Hookname: global_start
   
   PHP Code:

   ---

   $vbulletin->options['censorwords'] = $vbulletin->userinfo['fieldx']; 


   ---

Hack complete.

Anyway to do this with replacement variables instead of the built in censorship for vb?

I had the User Optional Censorship hack installed and I am still using the replacement variables to censor just now users can not turn it on and off....

You have got to be kidding me! Its that easy?

http://www.daily-web.info/forums/ima...s/SS_faint.gif

Didn't really test it, but theoretically that should be it.

Just gave it a try. No affect. I guess nothing is ever as easy as it seems.

I would think it would go in hooks global complete not start.

@FASherman
Tested and seems to work fine for me ...

Userfield is a single line text box with the words space delimited, right?

Yep. The postcache could be causing Problems though ...

Thats not the only problem. Go back and take a look at the contents of the userfield. :surprised:

Well, that's an even more serious Problem, LOL ^.^
Then most likely profile fields can't be used for this.

Yeah it won't work like that Kirby :(

The censor only checks as things go to the cache, after it's cached, it doesn't rerun on it, unless the post is editted.

I discovered this as I was workin on the censor per forums thing.

Turn the censor on for a forum, post a cuss word and it changes to %%%%.

Edit the message and it is %%%%

Turn the censor off, that post stays %%%%

Post a message with cuss words, and it doesn't change to %.

Turn the censor back on, and the cuss words in the pervious post still remain. However, if you edit the post with the cuss words, it reparses and changes to %%%%.



Damn... that's even more confusing typed out then it is in my head ;)

^ That is why I used the Replacement Variable Management and why I used the hack to make it optional for censorship for members.

Wish I could get it ported over :(