<?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>ANDY STRATTON&#187; Plugins</title>
	<atom:link href="http://theandystratton.com/category/wordpress/plugins/feed" rel="self" type="application/rss+xml" />
	<link>http://theandystratton.com</link>
	<description>WordPress and PHP Developer</description>
	<lastBuildDate>Wed, 18 Apr 2012 20:49:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Raw HTML Snippets WordPress&#160;Plugin</title>
		<link>http://theandystratton.com/2011/raw-html-snippets-wordpress-plugin</link>
		<comments>http://theandystratton.com/2011/raw-html-snippets-wordpress-plugin#comments</comments>
		<pubDate>Thu, 12 May 2011 15:16:52 +0000</pubDate>
		<dc:creator>andy</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://theandystratton.com/?p=531</guid>
		<description><![CDATA[Ever since my über vent over fake shortcodes that autoformat the output of real shortcodes, I realized that the intention was good but the execution was bad. So, I wrote a quick plugin that I thought was a more elegant (and that did not affect expected, core WordPress behaviors). Raw HTML Snippets This plugin allows [...]]]></description>
			<content:encoded><![CDATA[<p>Ever since my über vent over <a href="http://theandystratton.com/2011/shortcode-autoformatting-html-with-paragraphs-and-line-breaks">fake shortcodes that autoformat the output of real shortcodes</a>, I realized that the intention was good but the execution was bad.</p>
<p>So, I wrote a quick plugin that I thought was a more elegant (and that did not affect expected, core WordPress behaviors).</p>
<h2>Raw HTML Snippets</h2>
<p>This plugin allows you to create a library of raw HTML snippets you need to embed within post/page content, then uses the native shortcode API to embed them without them being auto-formatted by <code>wpautop</code> or <code>wptexturize</code>.</p>
<p>It may not be as convenient as pasting directly into the HTML tab of the WYSIWYG editor, but it&#8217;s a solution that&#8217;s reusable, clean and does not interfere with the core functionality of WordPress or other possible plugins/shortcodes/content filters.</p>
<p><a herf="http://wordpress.org/extend/plugins/raw-html-snippets/" rel="external">Raw HTML Snippets</a> | <a href="http://downloads.wordpress.org/plugin/raw-html-snippets.zip" rel="external">Download</a></p>
<p>Give it a whirl, and let me know what you think!</p>
]]></content:encoded>
			<wfw:commentRss>http://theandystratton.com/2011/raw-html-snippets-wordpress-plugin/feed</wfw:commentRss>
		<slash:comments>20</slash:comments>
		</item>
		<item>
		<title>BuddyPress Avatars Not Displaying with WordPress&#160;3.0</title>
		<link>http://theandystratton.com/2010/buddypress-avatars-not-displaying-with-wordpress-3-0</link>
		<comments>http://theandystratton.com/2010/buddypress-avatars-not-displaying-with-wordpress-3-0#comments</comments>
		<pubDate>Thu, 09 Sep 2010 15:13:26 +0000</pubDate>
		<dc:creator>andy</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://theandystratton.com/?p=488</guid>
		<description><![CDATA[I don&#8217;t work with BuddyPress much if at all, but have been doing a lot more of it lately. Recently, we had an issue where avatars were not displaying on pages using the built-in template tags, like bp_member_avatar() and others. We thought this was a weird environment issue at first, but then I found this [...]]]></description>
			<content:encoded><![CDATA[<p>I don&#8217;t work with BuddyPress much if at all, but have been doing a lot more of it lately. Recently, we had an issue where avatars were not displaying on pages using the built-in template tags, like <code>bp_member_avatar()</code> and others.</p>
<p>We thought this was a weird environment issue at first, but then I found <a href="http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/custom-avatars-not-showing-on-multisite-blogs/" rel="external">this post</a> that showed me it&#8217;s a common issue that&#8217;s been reported to their development team.</p>
<p>I continued searching for a solution and got some direction <a href="http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/custom-avatars-arent-shown-on-single-blogs-in-wpmu/" rel="external">from a solution</a> by <a href="http://buddypress.org/community/members/foralien/" rel="external">@foralien</a> on the BuddyPress forums. Her solution did not work for, but I created my own version and had success.</p>
<h2>What was happening?</h2>
<p>Our BuddyPress installation was trying to get avatars from <code>/blogs.dir/1/files/avatars/{$user_id}/{$filename}</code> – which did not eve exist, this was referencing a files directory for the root blog and it didn&#8217;t even exist.</p>
<p>As per <a href="http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/custom-avatars-arent-shown-on-single-blogs-in-wpmu/" rel="external">@foralien&#8217;s solution</a>, I created 2 filters (one for the avatar path, the other for the avatar public URL):</p>
<p><a href="/downloads/bp-avatar-filters.txt"><strong>Download the Code</strong></a></p>
<pre class="brush: php; title: ; notranslate">// Custom filters to clean up issues in WP 3.0 with avatar paths.
// Written by @theandystratton
function sizeable_bp_core_avatar_folder_dir( $path ) {
	$items = explode('/', $path);
	$path = ABSPATH . 'wp-content/uploads/avatars/' . end($items);
	return $path;
}
add_filter('bp_core_avatar_folder_dir', 'sizeable_bp_core_avatar_folder_dir');
function sizeable_bp_core_avatar_folder_url( $url ) {
	$items = explode('/', $url);
	$url = 'http://' . $items[2] . '/wp-content/uploads/avatars/' . end($items);
	return $url;
}
add_filter('bp_core_avatar_folder_url', 'sizeable_bp_core_avatar_folder_url');</pre>
<h2>What it&#8217;s doing</h2>
<p>We&#8217;re filtering the path and the url for avatars to ensure it&#8217;s using the WP 3.0 location, which is the upload_path for the root site followed by <code>/avatars/{$user_id}</code>. This is <em>not</em> a forever fix. I&#8217;d use it as duct tape until they release a BuddyPress update for WP 3.0 fixing the issue.</p>
<p>Hope this helps you guys and saves you some time and frustration.</p>
]]></content:encoded>
			<wfw:commentRss>http://theandystratton.com/2010/buddypress-avatars-not-displaying-with-wordpress-3-0/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>The Permalinker WordPress Plugin: Dynamic&#160;Permalinks</title>
		<link>http://theandystratton.com/2009/the-permalinker-wordpress-plugin-dynamic-permalinks</link>
		<comments>http://theandystratton.com/2009/the-permalinker-wordpress-plugin-dynamic-permalinks#comments</comments>
		<pubDate>Tue, 30 Jun 2009 18:48:21 +0000</pubDate>
		<dc:creator>andy</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://theandystratton.com/?p=181</guid>
		<description><![CDATA[As a developer, I&#8217;ve always found permalinks and directory structures between local, staging, and production environments to be a pain. Creating links within content requires either absolute (http://yourdomain.com/path/to/post/) or a non-domain-specific absolute (/install/directory/path/to/post) URLs. This can prove to be a pain during the development or migration process. It can also make it annoying if you [...]]]></description>
			<content:encoded><![CDATA[<p>As a developer, I&#8217;ve always found permalinks and directory structures between local, staging, and production environments to be a pain. Creating links within content requires either absolute (<code>http://yourdomain.com/path/to/post/</code>) or a non-domain-specific absolute (/install/directory/path/to/post) URLs.</p>
<p>This can prove to be a pain during the development or migration process. It can also make it annoying if you happen to change your permalink structure and have tons of posts.</p>
<p><strong class="header">Introducing dynamically inserted WordPress permalinks with The Permalinker</strong></p>
<p><a href="http://wordpress.org/extend/plugins/the-permalinker/" rel="external">The Permalinker</a> will allow you to use <a href="http://faq.wordpress.com/2008/06/18/what-are-the-wordpress-shortcodes/" rel="external">WordPress short codes</a> to dynamically insert permalinks and permalink URLs into your posts via the content editor.</p>
<p><strong>How it works:</strong></p>
<p>When editing content, simply use the the <code><a href="http://theandystratton.com/2009/the-permalinker-wordpress-plugin-dynamic-permalinks" class="permalinker_link "></code> short code to insert a link:</p>
<pre><code>[permalink]This is a link to the current post</a></code></pre>
<p><strong>Linking to a different post:</strong></p>
<p>You can set the <code>id</code> attribute in the short code to point to a specific page/post:</p>
<pre><code><a href="http://theandystratton.com/2009/9-revision-3" class="permalinker_link ">A link to post 23</a></code></pre>
<p><strong>Supported anchor attributes:</strong></p>
<p>Currently, the following attributes are supported in the <code><a href="http://theandystratton.com/2009/the-permalinker-wordpress-plugin-dynamic-permalinks" class="permalinker_link "></code> short code and will be added to the resulting anchor element: <code>class</code>, <code>rel</code>, and <code>target</code>.</p>
<pre><code>[permalink id=23 class="my_class" rel="self" target="_blank"]Open post 23 in a new window</a></code></pre>
<p><strong>Want more control over your markup?</strong></p>
<p>Using a non-terminating or empty <code>http://theandystratton.com/2009/the-permalinker-wordpress-plugin-dynamic-permalinks</code> short code will simply output the permalink URL:</p>
<pre><code>&lt;a href="http://theandystratton.com/2009/9-revision-3" class="thickbox" id="link_23">Another link to page/post 23&lt;/a&gt;</code></pre>
<p><strong class="header">There&#8217;s more: Dynamically grab your template directory</strong></p>
<p>As a request from fellow WordPress designers and developers, I&#8217;ve included a <code>http://theandystratton.com/wp-content/themes/theandystratton</code> short code as well, allowing you to quickly and dynamically get the full URL to your active template directory from the content editor:</p>
<pre><code>&lt;img src="http://theandystratton.com/wp-content/themes/theandystratton/photos/yoda.gif" alt="A picture of Yoda!" /&gt;</code></pre>
<p><strong class="header">Download Permalinker</strong></p>
<p>You can learn more and <a href="http://wordpress.org/extend/plugins/the-permalinker" rel="external">download The Permalinker</a> from the WordPress plugin repository.</p>
<p>Happy coding ;]</p>
]]></content:encoded>
			<wfw:commentRss>http://theandystratton.com/2009/the-permalinker-wordpress-plugin-dynamic-permalinks/feed</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Get WordPress Permalinks Working with Windows, IIS, and ISAPI&#160;Rewrite</title>
		<link>http://theandystratton.com/2009/get-wordpress-permalinks-working-with-windows-iis-and-isapi-rewrite</link>
		<comments>http://theandystratton.com/2009/get-wordpress-permalinks-working-with-windows-iis-and-isapi-rewrite#comments</comments>
		<pubDate>Wed, 29 Apr 2009 03:09:56 +0000</pubDate>
		<dc:creator>andy</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://theandystratton.com/?p=111</guid>
		<description><![CDATA[The eternal battle is over, mostly: getting your WordPress permalinks to work on your Windows IIS web server with ISAPI Rewrite installed. Some Requirments. Sorry, but you&#8217;re going to need ISAPI Rewrite 3. You can download a lite version for free, but I suggest purchasing it. I&#8217;ve used ISAPI Rewrite for years now with clients [...]]]></description>
			<content:encoded><![CDATA[<p>The eternal battle is over, mostly: getting your WordPress permalinks to work on your Windows IIS web server with ISAPI Rewrite installed.</p>
<p><strong>Some Requirments.</strong></p>
<ol>
<li>Sorry, but you&#8217;re going to need <a href="http://www.helicontech.com/isapi_rewrite/" rel="external">ISAPI Rewrite 3</a>. You can download a lite version for free, but I suggest purchasing it. I&#8217;ve used ISAPI Rewrite for years now with clients on Windows hosting, and it&#8217;s the bees knees. Version 3 is now supporting many common mod_rewrite directives, which is sweet.</li>
<li>Your <code>.htaccess</code> file. Here&#8217;s an example that has worked with WordPress 2.7.x, ISAPI Rewrite 3, and Windows Server 2003/IIS 6.0:
<pre class="brush: plain; title: ; notranslate">
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule .* /index.php [L]
</pre>
</li>
</ol>
<p><strong>How it works.</strong><br />
Even with ISAPI Rewrite, your WordPress permalinks most likely will be broken without the ugly, prepended <code>/index.php/</code>. The problem is that the <code>REQUEST_URI</code> server variable is not sent by IIS or ISAPI Rewrite. This plugin solves this.</p>
<p>This solution is more elegant that changing the WordPress core files because it allows you to easily upgrade WordPress without additional maintenance.</p>
<p><strong>Download and Documentation.</strong><br />
You can <a href="http://downloads.wordpress.org/plugin/isapi-rewriter.zip" rel="external">download ISAPI Rewriter</a> from the <a href="http://wordpress.org/extend/plugins/" rel="external">WordPress Plugin</a> directory.</p>
<p>You can view documentation at the <a href="http://wordpress.org/extend/plugins/isapi-rewriter/" rel="external">ISAPI Rewrite plugin</a> page.</p>
]]></content:encoded>
			<wfw:commentRss>http://theandystratton.com/2009/get-wordpress-permalinks-working-with-windows-iis-and-isapi-rewrite/feed</wfw:commentRss>
		<slash:comments>59</slash:comments>
		</item>
	</channel>
</rss>

