<?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: WordPress with Page Cacheing</title>
	<atom:link href="http://boakes.org/now-with-added-page-cacheing/feed/" rel="self" type="application/rss+xml" />
	<link>http://boakes.org/now-with-added-page-cacheing/</link>
	<description>A place for words and data that I publish (for the benefit of persons unknown).</description>
	<lastBuildDate>Mon, 30 Jan 2012 17:00:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: rich boakes</title>
		<link>http://boakes.org/now-with-added-page-cacheing/comment-page-1/#comment-2003</link>
		<dc:creator>rich boakes</dc:creator>
		<pubDate>Fri, 15 Jul 2005 15:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://boakes.org/now-with-added-page-cacheing#comment-2003</guid>
		<description>I&#039;ve seen no problems with old data yet.  Whenever I write or update an article or a comment, the cache is suitably purged.  Specifically, having just checked, I can confirm that when I submitted this comment the entire cache was purged, and the same thing happened when I added this extra sentence - adds and updates purge everything.

Basically it appears that any purging is total, so it&#039;s not (yet?) possible to, manually point-click-remove individual pages from the cache.

It&#039;s also worth noting that it correctly caches different versions of the same page, which is useful because for my logged in access I use a different theme that has added admin functions.

There is also a small issue with plugins like StatTraq that are unrelated to the displayed content. Where the cache streamlines things by not calling most of the code, these plugins don&#039;t get called either.  I had to manually alter the index.php to inform StatTraq whenever a page is requested.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen no problems with old data yet.  Whenever I write or update an article or a comment, the cache is suitably purged.  Specifically, having just checked, I can confirm that when I submitted this comment the entire cache was purged, and the same thing happened when I added this extra sentence &#8211; adds and updates purge everything.</p>
<p>Basically it appears that any purging is total, so it&#8217;s not (yet?) possible to, manually point-click-remove individual pages from the cache.</p>
<p>It&#8217;s also worth noting that it correctly caches different versions of the same page, which is useful because for my logged in access I use a different theme that has added admin functions.</p>
<p>There is also a small issue with plugins like StatTraq that are unrelated to the displayed content. Where the cache streamlines things by not calling most of the code, these plugins don&#8217;t get called either.  I had to manually alter the index.php to inform StatTraq whenever a page is requested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://boakes.org/now-with-added-page-cacheing/comment-page-1/#comment-2002</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Fri, 15 Jul 2005 15:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://boakes.org/now-with-added-page-cacheing#comment-2002</guid>
		<description>I&#039;ve been looking for a description of how the flushing works and what exactly will be flushed, and this is the closest thing I&#039;ve found.  The strange thing is that the plugin homeage has no mention of this.  Are there any issues with old content being held on to?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been looking for a description of how the flushing works and what exactly will be flushed, and this is the closest thing I&#8217;ve found.  The strange thing is that the plugin homeage has no mention of this.  Are there any issues with old content being held on to?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

