<?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; WordPress 2.5</title>
	<atom:link href="http://maisonbisson.com/blog/post/tag/wordpress-25/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>Mon, 23 Nov 2009 16:21:01 +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>WordPress 2.5 Out, MaisonBisson Upgraded</title>
		<link>http://maisonbisson.com/blog/post/12113/wordpress-25-out-maisonbisson-upgraded/</link>
		<comments>http://maisonbisson.com/blog/post/12113/wordpress-25-out-maisonbisson-upgraded/#comments</comments>
		<pubDate>Sun, 30 Mar 2008 06:38:06 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[concurrent editing protection]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[WordPress 2.5]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=12113</guid>
		<description><![CDATA[
WordPress 2.5 is out (and the WordPress site got a facelift), and I&#8217;ve already upgraded MaisonBisson using SVN. The changes are exciting, and seem to reflect a tradition that&#8217;s developing in WordPress of delivering some really revolutionary features in the x.5 release.
The loss of file-based object caching was a bit of a problem, as my [...]]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-12113"><!-- &nbsp; --></abbr>
<p><a href="http://wordpress.org/development/2008/03/wordpress-25-brecker/" title="WordPress › Blog » WordPress 2.5">WordPress 2.5</a> is out (and the <a href="http://wordpress.org/" title="WordPress › Blog Tool and Weblog Platform">WordPress</a> site got a facelift), and I&#8217;ve already upgraded MaisonBisson <a href="http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion">using SVN</a>. The changes are exciting, and seem to reflect a tradition that&#8217;s developing in WordPress of delivering some really revolutionary features in the x.5 release.</p>
<p>The loss of file-based object caching was a bit of a problem, as my <img src="http://www.lduhtrp.net/image-2621476-10436176" width="1" height="1" border="0"/><a href="http://www.anrdoezrs.net/click-2621476-10436176" target="_top">VPS</a>&#8217;s load average jumped to over 30 pretty quickly after the upgrade. I tried <a href="http://txfx.net/">Mark Jaquith</a>&#8217;s <a href="http://txfx.net/files/wordpress/apc-object-cache.phps" title="apc-object-cache.phps">apc-object-cache</a> enabler and saw load average drop back to 2 or so, but I also saw tag and category names disappear and discovered other weirdness. Why it happened I don&#8217;t know, but I&#8217;m looking into it. Fortunately, <a href="http://neosmart.net/" title="NeoSmart Technologies">NeoSmart</a>&#8217;s <a href="http://neosmart.net/blog/2008/file-based-extension-to-the-wordpress-object-cache/" title="File-Based Extension to the WordPress Object Cache — The NeoSmart Files">file-based object cache</a> replacement works perfectly and efficiently. (Mind you, <a href="http://boren.nu/" title="boren.nu">Ryan Boren</a> thinks <a href="http://boren.nu/archives/2007/06/11/wordpress-schwag-cache/" title="» WordPress Schwag Cache boren.nu">WordPress caches should require more adventure</a>.)</p>
<p><a href="http://maisonbisson.com/blog/bsuite">bSuite</a> seems to work perfectly in 2.5, though the new <a href="http://codex.wordpress.org/Shortcode_API" title="Shortcode API « WordPress Codex">shortcode API</a> obviates one of <a href="http://maisonbisson.com/blog/bsuite/tokens">bSuite&#8217;s coolest features: tokens</a>. Still, it&#8217;s better to run with the herd, so I&#8217;ll be transitioning bSuite&#8217;s built in tokens to take advantage of the shortcode API soon.</p>
<p>One of the features that&#8217;s not received much attention yet, but is hugely valuable to those (like me) who are using and advocating for WordPress as a general purpose CMS, is the concurrent editing protection. That is, if another WordPress author is editing a story, you can&#8217;t save changes to it until that editor is done. The next step for this is to allow concurrent team editing in <a href="http://www.google.com/support/writely/bin/answer.py?answer=44677&amp;topic=8625">the way Google Docs does</a> as well as versioning (versioning has been discussed as a feature for 2.6).</p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/12113/wordpress-25-out-maisonbisson-upgraded/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>WordPress 2.5 Offers Built-In Gravatar Support</title>
		<link>http://maisonbisson.com/blog/post/12099/wordpress-25-offers-built-in-gravatar-support/</link>
		<comments>http://maisonbisson.com/blog/post/12099/wordpress-25-offers-built-in-gravatar-support/#comments</comments>
		<pubDate>Thu, 06 Mar 2008 16:48:35 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[gravatar]]></category>
		<category><![CDATA[theme design]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[WordPress 2.5]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/blog/post/12099/wordpress-25-offers-built-in-gravatar-support</guid>
		<description><![CDATA[
Nobody doubted that full Gravatar support would make it into WordPress eventually. Weblog Tools Collection shows what they look like, how they&#8217;re managed, and how theme designers can implement them.
]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-12099"><!-- &nbsp; --></abbr>
<p>Nobody doubted that full <a href="http://site.gravatar.com/">Gravatar</a> support would make it into WordPress eventually. <a href="http://weblogtoolscollection.com/archives/2008/03/03/gravatars-and-wordpress-25/" title="Weblog Tools Collection » Blog Archive » Gravatars and WordPress 2.5">Weblog Tools Collection</a> shows what they look like, how they&#8217;re managed, and how theme designers can implement them.</p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/12099/wordpress-25-offers-built-in-gravatar-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changes To WordPress Object Caching In 2.5</title>
		<link>http://maisonbisson.com/blog/post/12087/changes-to-wordpress-object-caching-in-25/</link>
		<comments>http://maisonbisson.com/blog/post/12087/changes-to-wordpress-object-caching-in-25/#comments</comments>
		<pubDate>Thu, 07 Feb 2008 11:20:32 +0000</pubDate>
		<dc:creator>Casey Bisson</dc:creator>
				<category><![CDATA[Dispatches]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[cache]]></category>
		<category><![CDATA[changes]]></category>
		<category><![CDATA[object cache]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[WordPress 2.5]]></category>
		<category><![CDATA[wp-cache]]></category>

		<guid isPermaLink="false">http://maisonbisson.com/blog/post/12087/changes-to-wordpress-object-caching-in-25</guid>
		<description><![CDATA[
Jacob Santos&#8216; FuncDoc notes:
The WordPress Object Cache changed in WordPress 2.5 and removed a lot of file support from the code. This means that the Object Cache in WordPress 2.5 is completely dependent on memory and will not be saved to disk for retrieval later. The constant WP_CACHE also changed its meaning.
I&#8217;ve just started using [...]]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="maisonbisson-12087"><!-- &nbsp; --></abbr>
<p><a href="http://www.santosj.name/">Jacob Santos</a>&#8216; <a href="http://funcdoc.wordpress.com/2008/01/30/replacing-wordpress-object-caching/" title="Replacing WordPress Object Caching « Function Documentation">FuncDoc</a> notes:</p>
<blockquote><p>The WordPress Object Cache changed in WordPress 2.5 and removed a lot of file support from the code. This means that the Object Cache in WordPress 2.5 is completely dependent on memory and will not be saved to disk for retrieval later. The constant WP_CACHE also changed its meaning.</p></blockquote>
<p>I&#8217;ve just started using the <a href="http://codex.wordpress.org/Function_Reference/WP_Cache">object cache</a> and I&#8217;m happy with how it works now, so these changes are somewhat concerning. On the other hand, I&#8217;m confident that I&#8217;ll see even more performance gains once I get my head around the new cache and figure out how to implement it. </p>
<p>Extra: <a href="http://blog.ftwr.co.uk/wordpress/wp-cache-inspect/">Peter Westwood&#8217;s Cache Inspect</a> looks useful.</p>
]]></content:encoded>
			<wfw:commentRss>http://maisonbisson.com/blog/post/12087/changes-to-wordpress-object-caching-in-25/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>