<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>nMedia Interactive</title>
	<atom:link href="http://www.nmediainteractive.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nmediainteractive.com</link>
	<description>New Media to the Nth level.</description>
	<lastBuildDate>Fri, 18 May 2007 15:15:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New WordPress plug-in released: ToggleTracking</title>
		<link>http://www.nmediainteractive.com/2007/05/18/toggle-tracking-released/</link>
		<comments>http://www.nmediainteractive.com/2007/05/18/toggle-tracking-released/#comments</comments>
		<pubDate>Fri, 18 May 2007 15:15:43 +0000</pubDate>
		<dc:creator>Chris Gray</dc:creator>
				<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://home-appserver/nMediaInteractive/index.php/archives/5</guid>
		<description><![CDATA[WordPress Theme switching can be a pain
WordPress Themes are great but can present a few issues when you decide to change to a new theme. If you are like me, you may not be satisfied with a stock theme and tend to do a little “tweaking” after the fact. At a minimum, I always add [...]]]></description>
			<content:encoded><![CDATA[<p><strong>WordPress Theme switching can be a pain</strong><br />
WordPress Themes are great but can present a few issues when you decide to change to a new theme. If you are like me, you may not be satisfied with a stock theme and tend to do a little “tweaking” after the fact. At a minimum, I always add a number of tracking scripts (<a href="http://www.google.com/analytics">Google Analytics</a>, <a href="http://www.mybloglog.com/">MyBlogLog</a>, <a href="http://www.blogcatalog.com/">BlogCatalog</a>) to the head section (&lt;head&gt;&lt;/head&gt;) of my blog allowing me to track site usage. The problem with “tweaking” is that every time I change templates I need to transfer these “tweaks” to my new theme. This process is not that difficult but can be rather time consuming (and can also lend itself to error).</p>
<p><strong>My solution </strong><br />
With that being said, I thought it was time to investigate an automated solution. I searched for a plug-in that could move my tweaks to a new theme upon theme activation but was unable to find anything remotely close&#8230;so I decided to roll my own solution.</p>
<p>I have created a plug-in that takes your tracking code and stores it in the WordPress database. From there the plug-in hooks into <a href="http://codex.wordpress.org/The_Loop">The Loop</a> so that the tracking code shows up on each page. I also added a feature that allows you to turn this tracking code on/off. This feature is useful if you have a sandboxed WordPress installation (used to test template changes away from your production server) and do not want to skew your stats by repeated testing.</p>
<p>If you are interested in downloading this plug-in you can get it here:<a href="index.php/toggletracking"></p>
<h4 style="margin: 0px; padding: 0px">Download ToggleTracking 1.0 WordPress Plug-in</h4>
<p></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nmediainteractive.com/2007/05/18/toggle-tracking-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

