<?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: 5 Essential Tips for Overcoming WordPress 2.8 Performance Problems</title>
	<atom:link href="http://counsellingresource.com/features/2009/08/15/5-essential-tips-for-wordpress-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://counsellingresource.com/features/2009/08/15/5-essential-tips-for-wordpress-performance/</link>
	<description>Looking at life through the prism of psychology, philosophy, mental health and more. Originally created by counsellor, psychotherapist and philosopher Dr Greg Mulhauser, this blog is now the work of an international team of contributors.</description>
	<lastBuildDate>Fri, 19 Mar 2010 22:50:40 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dr Greg Mulhauser, Managing Editor</title>
		<link>http://counsellingresource.com/features/2009/08/15/5-essential-tips-for-wordpress-performance/#comment-51007</link>
		<dc:creator>Dr Greg Mulhauser, Managing Editor</dc:creator>
		<pubDate>Sun, 06 Sep 2009 21:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://counsellingresource.com/features/?p=1874#comment-51007</guid>
		<description>Hi Steve,

This would be a job for some much more in-depth investigation than I&#039;d be able to offer here. Speaking very &lt;em&gt;generally&lt;/em&gt;, without knowing the details, my top recommendations would be 1) restore from backup and try again, 2) use phpMyAdmin to check/repair database tables, and 3) restore from backup, then use phpMyAdmin to check/repair, then try again.

All the best,
Greg</description>
		<content:encoded><![CDATA[<p>Hi Steve,</p>
<p>This would be a job for some much more in-depth investigation than I&#8217;d be able to offer here. Speaking very <em>generally</em>, without knowing the details, my top recommendations would be 1) restore from backup and try again, 2) use phpMyAdmin to check/repair database tables, and 3) restore from backup, then use phpMyAdmin to check/repair, then try again.</p>
<p>All the best,<br />
Greg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve</title>
		<link>http://counsellingresource.com/features/2009/08/15/5-essential-tips-for-wordpress-performance/#comment-51006</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Sun, 06 Sep 2009 20:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://counsellingresource.com/features/?p=1874#comment-51006</guid>
		<description>I just upgraded a friend to wp v2.8.4. Now all her comments have disappeared. She had no activated plug-ins. I&#039;m in desperate need of finding a way of bringing all of her comments back. Can you help? Thanks.</description>
		<content:encoded><![CDATA[<p>I just upgraded a friend to wp v2.8.4. Now all her comments have disappeared. She had no activated plug-ins. I&#8217;m in desperate need of finding a way of bringing all of her comments back. Can you help? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr Greg Mulhauser, Managing Editor</title>
		<link>http://counsellingresource.com/features/2009/08/15/5-essential-tips-for-wordpress-performance/#comment-50929</link>
		<dc:creator>Dr Greg Mulhauser, Managing Editor</dc:creator>
		<pubDate>Mon, 17 Aug 2009 09:53:36 +0000</pubDate>
		<guid isPermaLink="false">http://counsellingresource.com/features/?p=1874#comment-50929</guid>
		<description>Hi Ben,

It&#039;s tough to make a specific recommendation without knowing lots of details about your operating environment and individual needs, but my general approach is to ask first whether there are any strong reasons &lt;em&gt;not&lt;/em&gt; to upgrade, and then go from there.

So if, for example, you have a plugin or two which cannot work with 2.8.x, that would be a reason not to upgrade. Problems with a theme not being able to work with the current version might be another reason not to upgrade. Those are probably the two most common barriers to upgrading.

If those don&#039;t apply to you, then I think keeping up with the latest version is generally a good idea for two reasons: 1) the major updates often contain scores and scores of bug fixes, and 2) the folks at the helm of WordPress often wind up telling the world just what is broken when they make a security release, indirectly but immediately putting all their users at risk except for those who update the moment a new release comes out. So if you&#039;d like to avoid those security risks and benefit from those bugfixes, staying with the latest version is the way to do it. (Yes, there definitely &lt;em&gt;are&lt;/em&gt; unknown risks associated with jumping straight into the latest and greatest shiny new release, but those unknown risks must be balanced against the &lt;em&gt;known&lt;/em&gt; risks of not doing so.)

All the best,
Greg</description>
		<content:encoded><![CDATA[<p>Hi Ben,</p>
<p>It&#8217;s tough to make a specific recommendation without knowing lots of details about your operating environment and individual needs, but my general approach is to ask first whether there are any strong reasons <em>not</em> to upgrade, and then go from there.</p>
<p>So if, for example, you have a plugin or two which cannot work with 2.8.x, that would be a reason not to upgrade. Problems with a theme not being able to work with the current version might be another reason not to upgrade. Those are probably the two most common barriers to upgrading.</p>
<p>If those don&#8217;t apply to you, then I think keeping up with the latest version is generally a good idea for two reasons: 1) the major updates often contain scores and scores of bug fixes, and 2) the folks at the helm of WordPress often wind up telling the world just what is broken when they make a security release, indirectly but immediately putting all their users at risk except for those who update the moment a new release comes out. So if you&#8217;d like to avoid those security risks and benefit from those bugfixes, staying with the latest version is the way to do it. (Yes, there definitely <em>are</em> unknown risks associated with jumping straight into the latest and greatest shiny new release, but those unknown risks must be balanced against the <em>known</em> risks of not doing so.)</p>
<p>All the best,<br />
Greg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Find Yourself with a Smile...</title>
		<link>http://counsellingresource.com/features/2009/08/15/5-essential-tips-for-wordpress-performance/#comment-50922</link>
		<dc:creator>Find Yourself with a Smile...</dc:creator>
		<pubDate>Sat, 15 Aug 2009 20:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://counsellingresource.com/features/?p=1874#comment-50922</guid>
		<description>I didn&#039;t expect to find this here, but it is actually very helpful.

I&#039;m still using 2.7.1.

Would you recommend upgrading to 2.8.4 (which I think is still the latest), or should I hold on a bit longer?

This is fun.  For bloggers, better software is a powerful tool to improve mental health... which might already be a bit shaky for those of us on the blogosphere  :-)

keep smiling,

BEn</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t expect to find this here, but it is actually very helpful.</p>
<p>I&#8217;m still using 2.7.1.</p>
<p>Would you recommend upgrading to 2.8.4 (which I think is still the latest), or should I hold on a bit longer?</p>
<p>This is fun.  For bloggers, better software is a powerful tool to improve mental health&#8230; which might already be a bit shaky for those of us on the blogosphere  :-)</p>
<p>keep smiling,</p>
<p>BEn</p>
]]></content:encoded>
	</item>
</channel>
</rss>
