<?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>Tinsology &#187; WordPress</title>
	<atom:link href="http://tinsology.net/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://tinsology.net</link>
	<description>Read Me</description>
	<lastBuildDate>Thu, 20 May 2010 02:41:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Seamless WordPress bbPress Integration</title>
		<link>http://tinsology.net/2009/05/seamless-wordpress-bbpress-integration/</link>
		<comments>http://tinsology.net/2009/05/seamless-wordpress-bbpress-integration/#comments</comments>
		<pubDate>Wed, 13 May 2009 18:37:21 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[bbPress]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=611</guid>
		<description><![CDATA[If you've ever installed bbPress you know that it supports several different levels of integration with an existing WordPress blog. By default you can integrate cookies, users, and even have access to WordPress functions. After all of this, however, the user will still experience two independent applications. Most likely the themes you are using were not made with each other in mind. This doesn't have to be the case, and if you're willing to get your hands dirty you can get your bbPress installation to look and feel as if it is entirely a part of WordPress. Here is an example of what this looks like: <a href="http://everythingdev.com/forum/" target="_blank">Example</a>. <a href="http://tinsology.net/2009/05/seamless-wordpress-bbpress-integration/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/wordpress-plugins-using-subversion/' rel='bookmark' title='Permanent Link: WordPress Plugins: Using Subversion'>WordPress Plugins: Using Subversion</a></li>
<li><a href='http://tinsology.net/2009/04/plugin-compatibility/' rel='bookmark' title='Permanent Link: Plugin Compatibility'>Plugin Compatibility</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/05/seamless-wordpress-bbpress-integration/feed/</wfw:commentRss>
		<slash:comments>34</slash:comments>
		</item>
		<item>
		<title>Plugin Compatibility</title>
		<link>http://tinsology.net/2009/04/plugin-compatibility/</link>
		<comments>http://tinsology.net/2009/04/plugin-compatibility/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 00:59:38 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Compatibility]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=520</guid>
		<description><![CDATA[For various reasons, there are some people out that who have chosen to hang onto older versions of WordPress. Personally I do not recommend this behavior, but as a plugin developer, you might not want to exclude these people from using your plugin. Does this mean you should refrain from using features that were implemented in later versions for the benefit of those who have not upgraded? Absolutely not. One thing you can do, however, is to emulate or implement the newer features your plugin relies on for older versions. 
 
This is actually very simple to do considering you <a href="http://tinsology.net/2009/04/plugin-compatibility/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/05/seamless-wordpress-bbpress-integration/' rel='bookmark' title='Permanent Link: Seamless WordPress bbPress Integration'>Seamless WordPress bbPress Integration</a></li>
<li><a href='http://tinsology.net/2009/04/plugin-review-hello-world/' rel='bookmark' title='Permanent Link: Plugin Review: Hello World'>Plugin Review: Hello World</a></li>
<li><a href='http://tinsology.net/2009/04/plugin-wp-simplemail/' rel='bookmark' title='Permanent Link: Plugin: WP SimpleMail'>Plugin: WP SimpleMail</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/plugin-compatibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Plugins: Using Subversion</title>
		<link>http://tinsology.net/2009/04/wordpress-plugins-using-subversion/</link>
		<comments>http://tinsology.net/2009/04/wordpress-plugins-using-subversion/#comments</comments>
		<pubDate>Sun, 26 Apr 2009 22:35:32 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[SVN]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=455</guid>
		<description><![CDATA[So you've written a WordPress plugin and its now time to upload it to the WordPress plugin repository. Your first step will be requesting that your plugin be hosted on <a title="Add Your Plugin" href="http://wordpress.org/extend/plugins/add/" target="_blank">WordPress' Plugin Directory</a>. Sometime later your request will be accepted (provided it doesn't drop all of the tables in the database or something like that) and you'll be given access to the Subversion Repository. <a href="http://tinsology.net/2009/04/wordpress-plugins-using-subversion/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/05/seamless-wordpress-bbpress-integration/' rel='bookmark' title='Permanent Link: Seamless WordPress bbPress Integration'>Seamless WordPress bbPress Integration</a></li>
<li><a href='http://tinsology.net/2009/05/wordpress-plugin-adshare/' rel='bookmark' title='Permanent Link: WordPress Plugin: AdShare'>WordPress Plugin: AdShare</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/wordpress-plugins-using-subversion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress XHTML Validation</title>
		<link>http://tinsology.net/2009/04/wordpress-xhtml-validation/</link>
		<comments>http://tinsology.net/2009/04/wordpress-xhtml-validation/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 23:00:45 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[(X)HTML/CSS/CMS]]></category>
		<category><![CDATA[Validation]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=296</guid>
		<description><![CDATA[Almost immediately after I started my blog I began having difficulties ensuring that my XHTML would validate. Most of the time I could fix it by modifying the code in a plugin that carelessly preventing my XHTML from validating. Almost always it was something trivial (ie using single quotes instead of double quotes or using CAPS in attributes), however one problem I had persisted for quite a while. 
 
These were the errors I was getting: 
<ul> 
 <li>end tag for element "div" which is not open</li> 
 <li>XML Parsing Error: Opening and ending tag mismatch: body</li> 
 <li>XML Parsing</li></ul> <a href="http://tinsology.net/2009/04/wordpress-xhtml-validation/">Read More</a>


No related posts.]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/wordpress-xhtml-validation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Scheduling</title>
		<link>http://tinsology.net/2009/03/wordpress-scheduling/</link>
		<comments>http://tinsology.net/2009/03/wordpress-scheduling/#comments</comments>
		<pubDate>Fri, 13 Mar 2009 08:01:54 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Random]]></category>
		<category><![CDATA[Death]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=176</guid>
		<description><![CDATA[Should I ever become terminally ill, I plan to make excessive use of the WordPress post scheduling feature so I appear to be blogging from beyond the grave.

By the way...
I wrote this on the 8th, but it wasn't published until the 13th. I might be dead already. :o <a href="http://tinsology.net/2009/03/wordpress-scheduling/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/05/seamless-wordpress-bbpress-integration/' rel='bookmark' title='Permanent Link: Seamless WordPress bbPress Integration'>Seamless WordPress bbPress Integration</a></li>
<li><a href='http://tinsology.net/2009/04/wordpress-xhtml-validation/' rel='bookmark' title='Permanent Link: WordPress XHTML Validation'>WordPress XHTML Validation</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/03/wordpress-scheduling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Configuring WP for Code Examples and Execution</title>
		<link>http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/</link>
		<comments>http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/#comments</comments>
		<pubDate>Wed, 14 Jan 2009 07:15:14 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[Display Code]]></category>
		<category><![CDATA[Execute PHP]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=30</guid>
		<description><![CDATA[Since launching this blog a few days ago I have yet to post and code examples or tutorials. In preperation for this, and having decided that plain text code examples just wouldn't cut it, I went searching for a plugin to format and highlight my code. Not too long afterward I came across the <a href="http://wordpress.org/extend/plugins/syntaxhighlighter/" target="_blank">SyntaxHighlighter</a> plugin. After a simple installation I was able to do things like this: <a href="http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/06/php-complex-variables-in-strings/' rel='bookmark' title='Permanent Link: PHP: Complex Variables in Strings'>PHP: Complex Variables in Strings</a></li>
<li><a href='http://tinsology.net/2009/05/inheriting-code/' rel='bookmark' title='Permanent Link: Inheriting Code'>Inheriting Code</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
