User-Configurable Censorship Options
 

Hi all,

This might sound like an odd hack, but I am looking for something that would allow users to toggle on/off the censorship feature of the site.

Would this be easy to do?

I have a site with a good number of teenage/young-adult users, some of which don't mind the occasional profanity, others who tend to be offended. I would like to give them the option to censor a default list of words. However, I don't want to do forum-wide censorship.

A "wish list" would include the option for users to individually set a list of words to be censored...

This would be an excellent Idea!

Satan

then code it satan ;)

actually this is doable, but you have to go throug some files to clean the censortext function out of it :)
change the censortext function in functions.php an other small things, not really hard to code, but timeintensive

Xenon is right.

And also IMO the most time intensive part is the SQL integration. You need an extra field in your database (probably in user table or you can make it a table on its own) and you need to code the section in USER CP and Admin CP to edit/modify this field. Adjust necessary templates etc..

It really takes time to code/debug but good idea so I hope somebody takes it on.

I would have liked to, until you said SQL integration;)

I leave that kinda stuff to you...

I might give it a go...Im pretty busy at the moment though, getting my friend's site back and working, and my site, and other numerous bits...

Satan

Not the simplest hack, since censoring is done *before* the post is inserted into the database. You'll need to change that and have it censor the post (title, private messages, events, etc.) on the fly.

Really? I havent noticed that before. IMO censoring the post before writing to db, is not the best practise. If Admin deletes a cencored word from the list, it stays cencored for all the existing posts. Probably they wanted to save the SQL query/CPU load for threadviews.

yes it is, but as i know in pms aso its the other way round.

this is why i said it'll take really time becaus you have to change the censororder often :)

I knew that it was done beforehand, otherwise I might have tried it myself (although that probably wouldn't have been a good idea anyway!) :)

I also think it would be better to do the censoring on-the-fly rather than sticking it in the database, since (for reasons already mentioned) it is always nice to have a "fresh copy" of posts in case settings change in the future. Although, would there be performance issues in doing it on-the-fly? It seems like the posts are already being parsed on-the-fly for things like vBB code, smilies, etc.

If any brave soul out there is thinking about giving it a shot, and would like someone to help test it or provide feedback, I'd be glad to help.

postings are censored before inserted in the db, and they are also censored on the fly....

theoretically you have to got through all files and delete the censoring before inserting in db. File like private.php, newreply.php, newthread.php, editpost.php, calendar.php aso.

then when there is only an on the fly censoring, it wouldn't be a problem anymore.
If you need help with the last step i can sure help you, but i won't go throug all files to find out the lines where you have to delete the censoring :)