Version: 0.4, by crs6785
Developer Last Online: May 2011
Category: End-User Options -
Version: 3.8.x
Rating:
Released: 02-23-2010
Last Update: 08-09-2010
Installs: 27
DB Changes Uses Plugins
Re-useable Code
No support by the author.
Info:
This mod allows a user to toggle word censorship from an option in their profile.
The following areas are covered by this mod:
Forum lists
Viewing threads/posts
Viewing user profiles
Groups
Albums
Who's Online list
Tags
Searches
Most private message stuff
Usertitles
It works by disabling censorship globally (so text gets into the database uncensored) and then selectively re-enabling it if the user has censorship enabled in their profile.
Installation:
Enable word censorship in the AdminCP area under vBulletin options and configure the words to block.
Import the XML file as a product under the 'Plugin System --> Manage Products' area of the AdminCP.
By default the censorship option in their profile will be checked, which disables word censorship.
You can change some product options for this mod by selecting the 'User Censorship Options' setting group from the vBulletin Options area in the AdminCP.
Uninstalling:
If you remove this product and want to stick with the normal vBulletin censoring system, then update the post cache and clear the parsed signatures under the 'Maintenance --> Update Counters' area of the AdminCP.
Changelog:
v0.1 (2/23/10)
Initial release
v0.2 (2/24/10)
Fix the plugin that censors group discussions.
Add a plugin to censor the pagetitle as set by navbits.
v0.3 (2/27/10)
Added an option to control if words are censored for visitors/unregistered users.
Added an option to control the default censorship value for newly registered users.
v0.4 (8/10/10)
Improved support for vBulletin 4.x.x (Thanks to CClements for the bug report and testing).
Fixed an issue in the group discussion plugin. Also added another plugin to cover censoring some pages that use the $pagetitle global variable.
I'm curious as to how this plugin performs on a moderate/large sized forum. Since it has to censor words in cached text, I'm guessing it might slow down loading cached posts. I'm curious if the delay/resources used is noticeable on a busy forum.
Any chance for a vb4 release? I tried installing this with vb 4.0.4 and it didn't work so well. Whenever I enabled censored words through my user profile, I got a screen full of code. I really like the idea, though, so I hope you can release a vb4 version if you have the time.
Any chance for a vb4 release? I tried installing this with vb 4.0.4 and it didn't work so well. Whenever I enabled censored words through my user profile, I got a screen full of code. I really like the idea, though, so I hope you can release a vb4 version if you have the time.
Interesting...what do you mean by screen full of code? You can PM the message/screenshot to me if you like.
I just tested the plugin with VB 4.0.5 and didn't see an issue like that when toggling the option in my profile. However, it could be that there is an issue with the logic that creates the custom user field, as it is created manually when the product is installed. That's just a guess though.
While I was testing VB 4 I also fixed the censoring in the forum bits plugin since it was changed a bit in VB 4. I'll still check if I can reproduce the issue with the option in the profile. If not I'll just upload the new version soon.
So with this mod I could censor, say, all profanity (that I can come up with lol), then the user themselves would be able to decide whether they want it on or off? That's exactly what I'm looking for if that's the case. I just want to make sure I understand this correctly
Second question... is censorship globally enabled automatically, and then the user can then decide they want it off or is it auto off, and the user can go turn it on? Also, for guests viewing, would the censorship be auto-on for them as well until they join and then they can turn it off? If not, is it possible to do this?
So with this mod I could censor, say, all profanity (that I can come up with lol), then the user themselves would be able to decide whether they want it on or off? That's exactly what I'm looking for if that's the case. I just want to make sure I understand this correctly
Yup, that's correct.
Quote:
Originally Posted by TheKdd
Second question... is censorship globally enabled automatically, and then the user can then decide they want it off or is it auto off, and the user can go turn it on? Also, for guests viewing, would the censorship be auto-on for them as well until they join and then they can turn it off? If not, is it possible to do this?
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...
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 ...
Code:
$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.
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...
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 ...
Code:
$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