<?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>MaisonBisson.com &#187; paths</title>
	<atom:link href="http://maisonbisson.com/blog/post/tag/paths/feed/" rel="self" type="application/rss+xml" />
	<link>http://maisonbisson.com</link>
	<description>A bunch of stuff I would have emailed you about.</description>
	<lastBuildDate>Sat, 14 Nov 2009 20:14:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Determining Paths and URLs In WordPress 2.6+</title>
		<link>http://maisonbisson.com/blog/post/12789/determining-paths-and-urls-in-wordpress-26/</link>
		<comments>http://maisonbisson.com/blog/post/12789/determining-paths-and-urls-in-wordpress-26/#comments</comments>
		<pubDate>Tue, 21 Oct 2008 15:28:21 +0000</pubDate>
		<dc:creator>Casey</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[constants]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[path]]></category>
		<category><![CDATA[paths]]></category>
		<category><![CDATA[plugins_url]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wp-content]]></category>
		<category><![CDATA[WP_CONTENT_DIR]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/?p=12789</guid>
		<description><![CDATA[
WP 2.6 allows sites to move the wp-content directory around, so plugin developers like me can&#8217;t depend on them being in a predictable location. We can look to the WP_CONTENT_DIR and WP_PLUGIN_DIR constants for answers, but a better solution is likely to use the X_url() functions. The most useful of those is likely to be [...]]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-12789"><!-- &nbsp; --></abbr>
<p>WP 2.6 allows sites to move the <code>wp-content</code> directory around, so plugin developers like me can&#8217;t depend on them being in a predictable location. We can look to the <a title="Determining Plugin and Content Directories « WordPress Codex" href="http://codex.wordpress.org/Determining_Plugin_and_Content_Directories"><code>WP_CONTENT_DIR</code> and <code>WP_PLUGIN_DIR</code> constants</a> for answers, but a better solution is likely to use the <a href="http://wpengineer.com/wordpress-return-url/"><code>X_url()</code> functions</a>. The most useful of those is likely to be <code>plugins_url()</code>. Even better, you can give these functions a relative path and they&#8217;ll return a fully qualified URL to the item.</p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/12789/determining-paths-and-urls-in-wordpress-26/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 2.6 Plugin and wp-config.php Path Changes</title>
		<link>http://maisonbisson.com/blog/post/12172/wordpress-26-plugin-and-wp-configphp-path-changes/</link>
		<comments>http://maisonbisson.com/blog/post/12172/wordpress-26-plugin-and-wp-configphp-path-changes/#comments</comments>
		<pubDate>Mon, 14 Jul 2008 14:29:11 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[paths]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[WordPress 2.6]]></category>
		<category><![CDATA[wp-content]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=12172</guid>
		<description><![CDATA[
Ozh&#8217;s tutorial explains the details, but the short story is that we&#8217;ll soon get WP_CONTENT_URL and WP_CONTENT_DIR constants. And this is more than just convenience, 2.6 allows site admins to put those directories anywhere they want, so the constants will be the only reliable way of finding that info.
]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-12172"><!-- &nbsp; --></abbr>
<p><a href="http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/" title="What Plugin Coders Must Know About WordPress 2.6 « planetOzh">Ozh&#8217;s tutorial explains the details</a>, but the short story is that we&#8217;ll soon get <code>WP_CONTENT_URL</code> and <code>WP_CONTENT_DIR</code> constants. And this is more than just convenience, 2.6 allows site admins to put those directories anywhere they want, so the constants will be the only reliable way of finding that info.</p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/12172/wordpress-26-plugin-and-wp-configphp-path-changes/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>