<?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>the Mittineague Blog &#187; Plugin</title>
	<atom:link href="http://www.mittineague.com/blog/tag/plugin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mittineague.com/blog</link>
	<description>Random rants and rambling ons, Observations and Opinion, Information and Instigation</description>
	<lastBuildDate>Mon, 06 Sep 2010 00:39:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=2.1</generator>
		<item>
		<title>Error Reporting Plugin Release Candidate</title>
		<link>http://www.mittineague.com/blog/2010/02/error-reporting-plugin-release-candidate/</link>
		<comments>http://www.mittineague.com/blog/2010/02/error-reporting-plugin-release-candidate/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 07:47:45 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Error Reporting]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=162</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2010/02/error-reporting-plugin-release-candidate/. The first version of the Error Reporting plugin became available in March of 2007. Since then there have been a few changes, most notably, the Ping Error with dashboard widget feature, and an Auto Delete of old error log files feature that has been added [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2010/02/error-reporting-plugin-release-candidate/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Clean Options Translations</title>
		<link>http://www.mittineague.com/blog/2009/06/clean-options-translations/</link>
		<comments>http://www.mittineague.com/blog/2009/06/clean-options-translations/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 03:03:54 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Clean Options]]></category>
		<category><![CDATA[i18n]]></category>
		<category><![CDATA[l10n]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[Translation]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=133</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2009/06/clean-options-translations/. Please Donate. No, I don&#039;t want your money. - Visit Mittineague - But if you are bilingual and fluent in English and another language, I will appreciate your help in providing translations. Beginning with version 1.2.0 the Clean Options plugin has a POT file in [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2009/06/clean-options-translations/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Ping Watcher Translations</title>
		<link>http://www.mittineague.com/blog/2009/04/ping-watcher-translations/</link>
		<comments>http://www.mittineague.com/blog/2009/04/ping-watcher-translations/#comments</comments>
		<pubDate>Sun, 05 Apr 2009 23:40:43 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[i18n]]></category>
		<category><![CDATA[l10n]]></category>
		<category><![CDATA[Ping Watcher]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[Translation]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=131</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2009/04/ping-watcher-translations/. I have decided that I should attempt to Internationalize my plugins so that they can be Localized. &#8212; i18n and l10n &#8212; but I need help! - Visit Mittineague - As the Ping Watcher plugin is the easiest of them for me to work with, [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2009/04/ping-watcher-translations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ping Watcher Plugin</title>
		<link>http://www.mittineague.com/blog/2009/04/ping-watcher-plugin/</link>
		<comments>http://www.mittineague.com/blog/2009/04/ping-watcher-plugin/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 07:23:04 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Ping Errors]]></category>
		<category><![CDATA[Ping List]]></category>
		<category><![CDATA[Ping Watcher]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=130</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2009/04/ping-watcher-plugin/. While checking the log files for errors found by the Error Reporting plugin, I&#039;ve noticed E_WARNING errors from failed pings. I&#039;ll admit, my ping list is a rather haphazard conglomerate of sites that I&#039;ve put together from various sources. From time to time one or [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2009/04/ping-watcher-plugin/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Page Specific CSS in WordPress Admin Pages</title>
		<link>http://www.mittineague.com/blog/2009/03/page-specific-css-in-wordpress-admin-pages/</link>
		<comments>http://www.mittineague.com/blog/2009/03/page-specific-css-in-wordpress-admin-pages/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 22:40:44 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Action]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Hook]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=129</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2009/03/page-specific-css-in-wordpress-admin-pages/. While working on the Clean Options plugin, I noticed in the source code that there was CSS from several plugins in the head section of all of the admin pages. Besides being unnecessary, there is also the potential problem that style rules intended for one [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2009/03/page-specific-css-in-wordpress-admin-pages/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Alternate Syntax</title>
		<link>http://www.mittineague.com/blog/2009/03/alternate-syntax/</link>
		<comments>http://www.mittineague.com/blog/2009/03/alternate-syntax/#comments</comments>
		<pubDate>Sun, 01 Mar 2009 07:57:30 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Clean Options]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=115</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2009/03/alternate-syntax/. Most commonly, the type of argument used in WordPress files for get_option() is a string. - Visit Mittineague - Some files however, use variables. i.e. $options = array('this', 'that', 'and', 'another'); foreach($options as $option) { get_option($option); } /* or */ foreach($options as $option) { get_option('prefix_' [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2009/03/alternate-syntax/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Clean Options Plugin Release Candidate</title>
		<link>http://www.mittineague.com/blog/2008/11/clean-options-plugin-release-candidate/</link>
		<comments>http://www.mittineague.com/blog/2008/11/clean-options-plugin-release-candidate/#comments</comments>
		<pubDate>Thu, 20 Nov 2008 06:11:22 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Clean Options]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=91</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2008/11/clean-options-plugin-release-candidate/. The first version of the Clean Options plugin became available in April of 2007. Since then there have been a few bug fixes, a few enhancements, a few version compatibility updates, and couple of minor tweaks. - Visit Mittineague - Two issues still remain that [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2008/11/clean-options-plugin-release-candidate/feed/</wfw:commentRss>
		<slash:comments>44</slash:comments>
		</item>
		<item>
		<title>Buttonsnap Hack</title>
		<link>http://www.mittineague.com/blog/2008/04/buttonsnap-hack/</link>
		<comments>http://www.mittineague.com/blog/2008/04/buttonsnap-hack/#comments</comments>
		<pubDate>Wed, 09 Apr 2008 19:03:16 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/?p=61</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2008/04/buttonsnap-hack/. During the upgrade to WordPress version 2.5 I got a &#034;Fatal Error&#034; while trying to activate a plugin. My first thought was that the plugin was not compatible with the new version, so I went to the plugin&#039;s page to look for an updated version [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2008/04/buttonsnap-hack/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clean Options RSS options</title>
		<link>http://www.mittineague.com/blog/2007/10/clean-options-rss-options/</link>
		<comments>http://www.mittineague.com/blog/2007/10/clean-options-rss-options/#comments</comments>
		<pubDate>Sat, 20 Oct 2007 03:41:49 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Clean Options]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/2007/10/clean-options-rss-options/</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2007/10/clean-options-rss-options/. The Clean Options plugin lists options named &#034;rss_(hash value)&#034; and &#034;rss_(hash value)_ts&#034;. Where do these options come from? WordPress uses the fetch_rss function to get content from RSS feeds. For example, the dashboard uses fetch_rss() to get incoming links, dev news (wordpress.org/development/feed/), and planet news [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2007/10/clean-options-rss-options/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Clean Options and Speed</title>
		<link>http://www.mittineague.com/blog/2007/09/clean-options-and-speed/</link>
		<comments>http://www.mittineague.com/blog/2007/09/clean-options-and-speed/#comments</comments>
		<pubDate>Tue, 25 Sep 2007 06:13:54 +0000</pubDate>
		<dc:creator>Mittineague</dc:creator>
				<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Clean Options]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.mittineague.com/blog/2007/09/clean-options-and-speed/</guid>
		<description><![CDATA[Copyright &#169; 2012 Mittineague. Visit the original article at http://www.mittineague.com/blog/2007/09/clean-options-and-speed/. In the blog article The 3 Easiest Ways to Speed Up WordPress, John Pozadzides discusses improving page load time. The Clean Options plugin can help by removing unnecessary rows from the wp_options table. How much does this speed up queries? Relatively, probably not much unless [...]]]></description>
		<wfw:commentRss>http://www.mittineague.com/blog/2007/09/clean-options-and-speed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

