<?xml version="1.0" encoding="UTF-8"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>WordPress &#8250; Support Topic: WP Super Cache conflicts with WP-BAN</title>
<link>http://wordpress.org/support/</link>
<description>WordPress &#8250; Support Topic: WP Super Cache conflicts with WP-BAN</description>
<language>en</language>
<pubDate>Thu, 26 Nov 2009 16:04:57 +0000</pubDate>

<item>
<title>donncha on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-1207938</link>
<pubDate>Fri, 11 Sep 2009 12:23:09 +0000</pubDate>
<dc:creator>donncha</dc:creator>
<guid isPermaLink="false">1207938@http://wordpress.org/support/</guid>
<description>&#60;p&#62;archon810 - unfortunately you probably shouldn't use the wp-ban plugin at all if you're using wp-super-cache
&#60;/p&#62;</description>
</item>
<item>
<title>masino_sinaga on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-1207760</link>
<pubDate>Fri, 11 Sep 2009 08:21:56 +0000</pubDate>
<dc:creator>masino_sinaga</dc:creator>
<guid isPermaLink="false">1207760@http://wordpress.org/support/</guid>
<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;Go to your &#60;strong&#62;WP Super Cache Manager&#60;/strong&#62; page from your admin panel, there is a directive just like this sentence below:&#60;/p&#62;
&#60;p&#62;&#60;code&#62;Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it&#38;#39;s enough to specify the year, i.e. &#38;#39;/2004/&#38;#39;. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.&#60;/code&#62;&#60;/p&#62;
&#60;p&#62;Have you tried to add the string related to your WP-Ban plugin to that directive above?&#60;/p&#62;
&#60;p&#62;[Sig removed. Please see forum guidelines. Mark]
&#60;/p&#62;</description>
</item>
<item>
<title>GamerZ on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-1207656</link>
<pubDate>Fri, 11 Sep 2009 04:24:53 +0000</pubDate>
<dc:creator>GamerZ</dc:creator>
<guid isPermaLink="false">1207656@http://wordpress.org/support/</guid>
<description>&#60;p&#62;Sorry can't think of it right now
&#60;/p&#62;</description>
</item>
<item>
<title>archon810 on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-1207484</link>
<pubDate>Fri, 11 Sep 2009 00:17:49 +0000</pubDate>
<dc:creator>archon810</dc:creator>
<guid isPermaLink="false">1207484@http://wordpress.org/support/</guid>
<description>&#60;p&#62;Bah, just found out I was banning a bunch of people because of this bug and didn't even notice because I had the &#34;disable wp-supercache for logged in users&#34; option.&#60;/p&#62;
&#60;p&#62;GamerZ, perhaps a more proper solution can be found than htaccess?
&#60;/p&#62;</description>
</item>
<item>
<title>GamerZ on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-1206724</link>
<pubDate>Thu, 10 Sep 2009 14:48:16 +0000</pubDate>
<dc:creator>GamerZ</dc:creator>
<guid isPermaLink="false">1206724@http://wordpress.org/support/</guid>
<description>&#60;p&#62;A quick workaround would be to use htaccess to ban IPs, &#60;a href=&#34;http://blamcast.net/articles/block-bots-hotlinking-ban-ip-htaccess&#34; rel=&#34;nofollow&#34;&#62;http://blamcast.net/articles/block-bots-hotlinking-ban-ip-htaccess&#60;/a&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>donncha on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-1206312</link>
<pubDate>Thu, 10 Sep 2009 08:44:03 +0000</pubDate>
<dc:creator>donncha</dc:creator>
<guid isPermaLink="false">1206312@http://wordpress.org/support/</guid>
<description>&#60;p&#62;Known issue, I don't use wp-ban so I can't offer a work around or fix.
&#60;/p&#62;</description>
</item>
<item>
<title>tony001 on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-1206279</link>
<pubDate>Thu, 10 Sep 2009 07:49:26 +0000</pubDate>
<dc:creator>tony001</dc:creator>
<guid isPermaLink="false">1206279@http://wordpress.org/support/</guid>
<description>&#60;p&#62;Same problem here - working on latest 2.8&#60;br /&#62;
This error does not appear to have been resolved and I suspect WP Super Cache is used quite frequently too so this does pose a problem.&#60;br /&#62;
Otherwise looks like a good plugin!
&#60;/p&#62;</description>
</item>
<item>
<title>kwdavids on "WP Super Cache conflicts with WP-BAN"</title>
<link>http://wordpress.org/support/topic/233601#post-953730</link>
<pubDate>Mon, 12 Jan 2009 20:02:02 +0000</pubDate>
<dc:creator>kwdavids</dc:creator>
<guid isPermaLink="false">953730@http://wordpress.org/support/</guid>
<description>&#60;p&#62;When a banned visitor (WP-BAN) visits the site, whatever page they hit returns a &#60;em&#62;ban&#60;/em&#62; message rather than the desired page. The &#60;em&#62;ban&#60;/em&#62; message gets cached (WP Super Cache), then every subsequent visitor to that page gets the ban message too. &#60;/p&#62;
&#60;p&#62;How can I prevent ban messages from being cached?
&#60;/p&#62;</description>
</item>

</channel>
</rss>
