<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WP Content Filter 1.0 &#8211; WordPress Plugin</title>
	<atom:link href="http://www.gwycon.com/wp-content-filter-wordpress-plugin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/</link>
	<description>Silverlight, WPF and C# .NET development</description>
	<lastBuildDate>Fri, 17 Jun 2011 23:02:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: David</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-343</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sun, 30 May 2010 21:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-343</guid>
		<description>Just to let everyone know, this plugin is back in active development. you can find the new official plugin page here: http://www.presscoders.com/plugins/free-plugins/wp-content-filter/

We also have support forums open for our free plugins. There is a small monthly subscription which gives you access to the support forums, and is basically in place to make sure that this plugin is kept up-to-date and give users peace of mind it will always be compatible with the latest version of WordPress, and that any bugs will be corrected as soon as possible.

You can find the forums here (just click the &#039;Register&#039; button if you wish to sign up): http://www.presscoders.com/forums/</description>
		<content:encoded><![CDATA[<p>Just to let everyone know, this plugin is back in active development. you can find the new official plugin page here: <a href="http://www.presscoders.com/plugins/free-plugins/wp-content-filter/" rel="nofollow">http://www.presscoders.com/plugins/free-plugins/wp-content-filter/</a></p>
<p>We also have support forums open for our free plugins. There is a small monthly subscription which gives you access to the support forums, and is basically in place to make sure that this plugin is kept up-to-date and give users peace of mind it will always be compatible with the latest version of WordPress, and that any bugs will be corrected as soon as possible.</p>
<p>You can find the forums here (just click the &#8216;Register&#8217; button if you wish to sign up): <a href="http://www.presscoders.com/forums/" rel="nofollow">http://www.presscoders.com/forums/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: o2</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-328</link>
		<dc:creator>o2</dc:creator>
		<pubDate>Fri, 19 Mar 2010 11:16:13 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-328</guid>
		<description>nice plugin. you may consider enhancing it by adding the ability to define what to replace keywords with, like forum filters.

it&#039;s a fun trick to replace say, &#039;moron&#039; with &#039;mellon&#039;</description>
		<content:encoded><![CDATA[<p>nice plugin. you may consider enhancing it by adding the ability to define what to replace keywords with, like forum filters.</p>
<p>it&#8217;s a fun trick to replace say, &#8216;moron&#8217; with &#8216;mellon&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-320</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 25 Feb 2010 03:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-320</guid>
		<description>FYI I have it running successfully on wordpress 2.9.2</description>
		<content:encoded><![CDATA[<p>FYI I have it running successfully on wordpress 2.9.2</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-319</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 25 Feb 2010 03:14:02 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-319</guid>
		<description>placing this code in wp-content-filter.php  (hacked from http://chumby.net/?p=44)

function str_replace_word($needle,$replacement,$haystack,$isInsen){
    if($isInsen == &quot;insen&quot;){
		$pattern = &quot;/\b$needle\b/i&quot;;
	} else {
		$pattern = &quot;/\b$needle\b/&quot;;
	}
    $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 == &quot;insen&quot;){
	  		$text = str_replace_word($sub_search, $tmp_search, $text, &quot;insen&quot;);
		}else{ 
	  		$text = str_replace_word($sub_search, $tmp_search, $text, &quot;&quot;);
		}

	} else { // EXISTING IPLEMENTATION
	  	if($filter_type == &quot;insen&quot;){
      		$text = str_ireplace($sub_search, $tmp_search, $text); 
		}else{ 
	  		$text = str_replace_word($sub_search, $tmp_search, $text, &quot;&quot;);
		}
	}

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 &quot;if (TRUE)&quot; code is the &quot;replace wholewords only&quot; checkbox that would be in the WP configuration options (if I knew how to do it )

Hope that helps</description>
		<content:encoded><![CDATA[<p>placing this code in wp-content-filter.php  (hacked from <a href="http://chumby.net/?p=44" rel="nofollow">http://chumby.net/?p=44</a>)</p>
<p>function str_replace_word($needle,$replacement,$haystack,$isInsen){<br />
    if($isInsen == &#8220;insen&#8221;){<br />
		$pattern = &#8220;/\b$needle\b/i&#8221;;<br />
	} else {<br />
		$pattern = &#8220;/\b$needle\b/&#8221;;<br />
	}<br />
    $haystack = preg_replace($pattern, $replacement, $haystack);<br />
    return $haystack;<br />
}</p>
<p>AND THEN  modifying the string replace towards the bottom of that page like this </p>
<p>	if (true){ // IT IS A WHOLE WORD REPLACE &#8211; FROM CONFIG </p>
<p>		if($filter_type == &#8220;insen&#8221;){<br />
	  		$text = str_replace_word($sub_search, $tmp_search, $text, &#8220;insen&#8221;);<br />
		}else{<br />
	  		$text = str_replace_word($sub_search, $tmp_search, $text, &#8220;&#8221;);<br />
		}</p>
<p>	} else { // EXISTING IPLEMENTATION<br />
	  	if($filter_type == &#8220;insen&#8221;){<br />
      		$text = str_ireplace($sub_search, $tmp_search, $text);<br />
		}else{<br />
	  		$text = str_replace_word($sub_search, $tmp_search, $text, &#8220;&#8221;);<br />
		}<br />
	}</p>
<p>Gives us a WHOLE WORD ONLY replacement  &#8211; what I would think is more useful. It uses a regular expression to find the whole words only.<br />
The &#8220;if (TRUE)&#8221; code is the &#8220;replace wholewords only&#8221; checkbox that would be in the WP configuration options (if I knew how to do it )</p>
<p>Hope that helps</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sakthi Ganesh</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-304</link>
		<dc:creator>Sakthi Ganesh</dc:creator>
		<pubDate>Tue, 24 Nov 2009 08:12:44 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-304</guid>
		<description>I have found some issues with my setup ( may be with this plugin)

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 ?</description>
		<content:encoded><![CDATA[<p>I have found some issues with my setup ( may be with this plugin)</p>
<p>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”.</p>
<p>But what it happened is<br />
It blocked the words that start with particular three letter word .For example it blocked and replaced theword</p>
<p>“Assets” with ” ***ets ” which one i didn’t expected</p>
<p>For example the line is become</p>
<p>To protect the digital ***ets( which one is gone meaningless )</p>
<p>Is that any solution for that ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Detoam</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-299</link>
		<dc:creator>Detoam</dc:creator>
		<pubDate>Sat, 19 Sep 2009 18:33:20 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-299</guid>
		<description>Awesome plug-in. I swear like there&#039;s no tomorrow on my blogs. Some ppl apparently don&#039;t like that. So thank You.
It does work in wp 2.8.4</description>
		<content:encoded><![CDATA[<p>Awesome plug-in. I swear like there&#8217;s no tomorrow on my blogs. Some ppl apparently don&#8217;t like that. So thank You.<br />
It does work in wp 2.8.4</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gestroud</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-298</link>
		<dc:creator>gestroud</dc:creator>
		<pubDate>Fri, 18 Sep 2009 04:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-298</guid>
		<description>Some additional words for the list :-)

Circumstance
Circumference
Constitutional Law
Passable</description>
		<content:encoded><![CDATA[<p>Some additional words for the list <img src='http://www.gwycon.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Circumstance<br />
Circumference<br />
Constitutional Law<br />
Passable</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-292</link>
		<dc:creator>David</dc:creator>
		<pubDate>Wed, 29 Jul 2009 12:59:02 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-292</guid>
		<description>Hi Liz,

I&#039;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 &#039;passenger&#039; 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 &#039;passenger&#039; is obviously a word that shouldn&#039;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 &#039;passenger&#039; 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</description>
		<content:encoded><![CDATA[<p>Hi Liz,</p>
<p>I&#8217;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 &#8216;passenger&#8217; word as it appears on your blog match one of your keywords in the plug-in list.</p>
<p>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 &#8216;passenger&#8217; is obviously a word that shouldn&#8217;t be filtered even though it contains a match for one of your keywords to filter.</p>
<p>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. </p>
<p>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 &#8216;passenger&#8217; 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).</p>
<p>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!</p>
<p>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.</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liz</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-291</link>
		<dc:creator>Liz</dc:creator>
		<pubDate>Wed, 29 Jul 2009 12:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-291</guid>
		<description>Thanks for the plugin. 
Have I configured something wrong?  
&#039;passenger&#039; is appearing as &#039;p***enger&#039;.  clearly filtering &#039;a**&#039;.
Not really my intention.</description>
		<content:encoded><![CDATA[<p>Thanks for the plugin.<br />
Have I configured something wrong?<br />
&#8216;passenger&#8217; is appearing as &#8216;p***enger&#8217;.  clearly filtering &#8216;a**&#8217;.<br />
Not really my intention.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim</title>
		<link>http://www.gwycon.com/wp-content-filter-wordpress-plugin/comment-page-1/#comment-288</link>
		<dc:creator>Kim</dc:creator>
		<pubDate>Thu, 23 Jul 2009 15:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://gwycon.com/?p=1112#comment-288</guid>
		<description>Thanks for replying back.  The plugin works flawlessly for me expect this issue.  I&#039;ll have a coder look into the css files to see if there is anything going on.  

Thanks again for getting back with me. Your time is appreciated.</description>
		<content:encoded><![CDATA[<p>Thanks for replying back.  The plugin works flawlessly for me expect this issue.  I&#8217;ll have a coder look into the css files to see if there is anything going on.  </p>
<p>Thanks again for getting back with me. Your time is appreciated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

