function str_replace_word($needle,$replacement,$haystack,$isInsen){
if($isInsen == “insen”){
$pattern = “/\b$needle\b/i”;
} else {
$pattern = “/\b$needle\b/”;
}
$haystack = preg_replace($pattern, $replacement, $haystack);
return $haystack;
}

AND THEN modifying the string replace towards the bottom of that page like this

if (true){ // IT IS A WHOLE WORD REPLACE – FROM CONFIG

if($filter_type == “insen”){
$text = str_replace_word($sub_search, $tmp_search, $text, “insen”);
}else{
$text = str_replace_word($sub_search, $tmp_search, $text, “”);
}

} else { // EXISTING IPLEMENTATION
if($filter_type == “insen”){
$text = str_ireplace($sub_search, $tmp_search, $text);
}else{
$text = str_replace_word($sub_search, $tmp_search, $text, “”);
}
}

Gives us a WHOLE WORD ONLY replacement – what I would think is more useful. It uses a regular expression to find the whole words only.
The “if (TRUE)” code is the “replace wholewords only” checkbox that would be in the WP configuration options (if I knew how to do it )

Hope that helps

I have blacklisted the various offensive words using the filter textbox . one of the word is “ass” .I have included the conclusion that ,the plugin may find and replace the ” Three letter world” combination of “a”,”S”,”S” that forms the word “ass”.

But what it happened is
It blocked the words that start with particular three letter word .For example it blocked and replaced theword

“Assets” with ” ***ets ” which one i didn’t expected

For example the line is become

To protect the digital ***ets( which one is gone meaningless )

Is that any solution for that ?

Circumstance
Circumference
Constitutional Law
Passable

I’m afraid the limitation of the plug-in as it stands is that the list of keywords to filter does not distinguish between whole words or sub words. Therefore, the letters being filtered in the ‘passenger’ word as it appears on your blog match one of your keywords in the plug-in list.

This is not necessarily a shortcoming of the plug-in as people may try to hide profanities inside of other words in an attempt to keep them visible. In your case Liz this is an unwanted action as ‘passenger’ is obviously a word that shouldn’t be filtered even though it contains a match for one of your keywords to filter.

At the moment, the plug-in removes anything, wherever it encounters it, if it matches one of your chosen keywords. I am not too sure how useful it would be to include an option to simply ignore a keyword match for a case similar to yours, if it is found inside another word, for the reason mentioned earlier; as this would make it VERY easy for anyone to use profanities all over the place simply by enclosing them with other letters.

Perhaps a more elegant solution would be to have a second list of keywords that, if encountered, would be ignored by the content filter. So for example in your case Liz, the word ‘passenger’ could be entered into this second keyword list. Then, when it is encountered it is ignored (even though it contains a keyword that the current plug-in version would normally filter).

This way, you could override certain words that should NOT be filtered even though they may contain a sub word that flags a match in your profanity keywords. Plus, if another word had this profanity keyword embedded then it would still get filtered as normal!

I will be doing an update for this plug-in at some point which will include this update, but I cannot promise when this will be at the moment due to other project commitments.

David

Thanks again for getting back with me. Your time is appreciated.

Glad your host agreed to upgrade. Please remove the phpinfo.php page from public access as it could potentially be a security risk because it exposes a lot of server settings and configuration.

Hmm, not really sure what this problem is exactly. Could be the plug-in itself or a side effect of another one, but maybe just the plug-in itself.

It has been a while since I was working on this plug-in but as far as I remember I was simply altering the post feed when profanity keywords were encountered. No HTML/CSS was stripped intentionally. One thing to note is that any keyword in the html code will also be filtered so for example href=”somepath” and such code will be checked and replaced. This could potentially break some html code. But not sure if it is this that is causing your problem.

Unfortunately I am not actively developing the free WP plugins right now, as I am busy on other projects. I do intend to return to plugin develpoment and also some themes which I have not done before. The plug-ins need checking and updated to be compatible with the latest versions of WP, but as yet I do not know when I will have time for this.

David

The issue now is that any post that has an image in it, the words do not wrap around when the plug has the keywords in place. When I remove the keywords and update the plugin, the post is laid out correctly. Do you know what would cause this?