I looked at at the vb4 code since I kind of liked @kh99's idea and I knew he was on the right track. I was hoping in the post table "pagetext" the censored words were still there and in some magical way they were only parsed before storing as a "parsed-post". I kind of new this was wrong, but was still hoping. Anyway, no-go.
One problem I noticed was the check for censored words via "fetch_censored_text" occurs everywhere for different contexts. It simply censors the string without caring from where it came from. I think I would want to write an interim function for "Fetch_censored_text" which stores the censored words and the context from which it came. In this way you can store the censored text from other areas of the board. The title of the post for example, Social group messages or CMS articles.
If you just wanted to just handle the "post text" then of course that would simplify the process -- there would be no reason to store the context.
It looks to me that if we used "class_dm_threadpost.php" --> class method "vB_DataManager::verify_pagetext" and extend the class with a modified method "verify_pagetext" --> which would call a modified function "fetch_sensored_text", where we would store the sensor-ed words in the new table that was created. We could simply add a simple AJAX call to query and display the results, since only admins and maybe mods would be using it.
06-13-2014, 11:39 PM
Threaded Mode