<?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: Be Careful When Choosing A New Theme</title>
	<atom:link href="http://www.zanderchance.com/2009/02/28/be-careful-when-choosing-a-new-theme/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zanderchance.com/2009/02/28/be-careful-when-choosing-a-new-theme/</link>
	<description>The Best Super Affiliate You've Never Heard Of!</description>
	<lastBuildDate>Fri, 03 Feb 2012 22:49:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Zander</title>
		<link>http://www.zanderchance.com/2009/02/28/be-careful-when-choosing-a-new-theme/comment-page-1/#comment-773</link>
		<dc:creator>Zander</dc:creator>
		<pubDate>Tue, 03 Mar 2009 14:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.zanderchance.com/?p=803#comment-773</guid>
		<description>You&#039;re absolutely right - Had I planned this a little better, I could have saved a lot of time by editing the theme completely on the first site, and then exporting those changes for the rest of the sites.

Unfortunately, I never expected the theme to put this kind of load on our server.  Only when I dove into the code did I see the incredible number of redundant calls to the Database that could be eliminated by hard-coding some values into the theme.

Furthermore, each of my blogs have slight variations (colors, logos, sidebar content, etc), so each theme does need to be edited once it&#039;s uploaded.  It&#039;s proved to be a REALLY time consuming project.</description>
		<content:encoded><![CDATA[<p>You&#8217;re absolutely right &#8211; Had I planned this a little better, I could have saved a lot of time by editing the theme completely on the first site, and then exporting those changes for the rest of the sites.</p>
<p>Unfortunately, I never expected the theme to put this kind of load on our server.  Only when I dove into the code did I see the incredible number of redundant calls to the Database that could be eliminated by hard-coding some values into the theme.</p>
<p>Furthermore, each of my blogs have slight variations (colors, logos, sidebar content, etc), so each theme does need to be edited once it&#8217;s uploaded.  It&#8217;s proved to be a REALLY time consuming project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.zanderchance.com/2009/02/28/be-careful-when-choosing-a-new-theme/comment-page-1/#comment-772</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 03 Mar 2009 14:32:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.zanderchance.com/?p=803#comment-772</guid>
		<description>Why not just edit the theme on one site, export it via whatever FTP tool you use, and then import it onto all your other sites? That&#039;d keep the changes, while saving the hassle of doing it separately another 31 times.

I know you are probably over the problem now, but it&#039;s an obvious solution that&#039;d save time if you have the problem next time.

That&#039;s unless you wanted different things to be done to each blog?</description>
		<content:encoded><![CDATA[<p>Why not just edit the theme on one site, export it via whatever FTP tool you use, and then import it onto all your other sites? That&#8217;d keep the changes, while saving the hassle of doing it separately another 31 times.</p>
<p>I know you are probably over the problem now, but it&#8217;s an obvious solution that&#8217;d save time if you have the problem next time.</p>
<p>That&#8217;s unless you wanted different things to be done to each blog?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

