This hack doesn't use the vBulletin censorship system at all, so that would make no difference at all whether it's on or off. To get words filtered or replaced using this hack you must enter each one into the Replacement Variables system. It's a bit of a pain if you have a long list of words, but it is flexible and means that rather than have just asterisks (as with the vB censorship system) you can replace one word with another. For example, m*therf**ker could be replaced by muddyfunster.

I can't think of a reason why it wouldn't be working for you off the top of my head. I haven't upgraded my forum to 3.0.1 yet, nor do I have Microstats applied. All I can say is it "should work" if you've followed the instructions correctly, to the best of my knowledge.

If anyone else has had problems installing this, I'd be grateful to hear about it.

Ahh.. I thought it used the forum's censored words and bypassed the off switch.

My apologies.. I'm not with it at the moment.! ;)


Unfortunately, doing it via replacements censors "ass" in password for example.. Bah, it's a nice idea - but not quite what I wanted.

I just remembered why I disabled it for titles. The fact that, like Obliviaon Knight said, parts of words are censored, such as "ass." That's the same problem I ran into. No worries though. it's still better than the permanent *** censor. I will install this later tonight when I get home from work. :)

Hehe, fair comment. Where I live, "ass" is more likely to mean donkey than buttocks, so I don't even regard it as a candidate for censorship.

However, if it posed a problem, an administrator should be able to get round it by using 3 replacements. For example:

1. ass -> donkey

This has the undesired side-effect of changing password to "pdonkeyword" and "class" to "cldonkey". The abomination of "class" means that a lot of the CSS stuff up. However, if the admin also includes:

2. cldonkey -> class
3. pdonkeyword -> password

Then everything's fine. "ass password" gets rendered as "donkey password", and all the class= definitions in the source are also correct.

Whether an admin can be bothered to add a couple of extra replacements to "correct" any such problems really depends on how important the optional censorship is.

This is a very nice hack, i myself find it EXTREMLY aggrvating that i have to view edited ++++ even though i like to curse myself, therby not really caring if others do as well..

How do I turn on filtering by default to my registered users?

It doesn't appear to be working for me either and I went back and double, and triple-checked that I followed the instructions correctly. I also have 3.0.1 and Microstats installed, not sure if there's a correlation or not. It just censors words for everyone, regardless of the setting in their control panel.

I'd love to use this, we have a few potty mouths (me included) and a few others quite the opposite and this would be perfect!

You can do this by using the following SQL instead of the line in the instructions:

If you have already added this new column, you can set all the existing users to use the censorship by default using this:

This will set everyone to be using the censorship filter, and make it the default for all new users. Anyone that had it turned off will have to turn it off again if they want it that way.

I'm not sure about this as I don't have Microstats installed. If you give me a link ti the appropriate release thread I'll take a look at installing it and see if I can work out what the problem is.

I'm interested in this hack, but I'm brand new to vB3 and a bit put off by the caveat that use of the replacements system in this way might preclude its use in other ways. I guess I'm asking what potential I lose by using this, since I'm not really sure what else I would use replacements for.

Thanks!