[steeler7]

Originally Posted by crs6785

Yup, that's correct.



Currently I have it set so censorship is disabled by default for users when you install the product. You can change it if you want, but you'll need to edit the product manually before installing it. You would need to edit the following line of the install code...

$db->query_write("ALTER TABLE " . TABLE_PREFIX . "userfield ADD field{$profilefield_id} INT NOT NULL DEFAULT '1';");

And change the 1 near the end to a 0. So it would look like this ...

$db->query_write("ALTER TABLE " . TABLE_PREFIX . "userfield ADD field{$profilefield_id} INT NOT NULL DEFAULT '0';");

They can go into their profile at anytime then to change the censorship status. You can also set an option in the AdminCP to decide whether you want censorship enabled or disabled for new users (this will not change the option for current users).

You can also toggle censorship on or off for visitors from an option in the AdminCP. By default it is set to not censor text for visitors (easily changed though, like I mentioned).

I will be releasing a new version soon with some fixes for vbulletin4. I'm pretty sure I fixed the bug CClements pointed out. If I don't hear back in a week I'll post the new version since I'm pretty confident it's fixed.

Awesome! I've been looking for this when I had 3.8.4 and didn't see it and now that I upgraded to 4 I thought there was a slim chance to find this.

Thanks. I'm looking forward to the vB 4 release of this