<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Maybe_Serialize and the Magic of Wordpress</title>
	<atom:link href="http://apartmentonesix.com/2009/03/maybe_serialize-and-the-magic-of-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://apartmentonesix.com/2009/03/maybe_serialize-and-the-magic-of-wordpress/</link>
	<description></description>
	<lastBuildDate>Mon, 12 Jul 2010 12:35:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Widgetizing a Wordpress Plugin: Example Widget Code &#124; Apartment One Six</title>
		<link>http://apartmentonesix.com/2009/03/maybe_serialize-and-the-magic-of-wordpress/comment-page-1/#comment-113</link>
		<dc:creator>Widgetizing a Wordpress Plugin: Example Widget Code &#124; Apartment One Six</dc:creator>
		<pubDate>Sat, 18 Apr 2009 17:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://apartmentonesix.com/?p=72#comment-113</guid>
		<description>[...] First, we get the option we&#8217;re going to use to store the configuration infomation for this widget. If it doesnt exist (meaning that this is the first time the widget code has been run, so our plugin has likely just been installed), we&#8217;ll create it with some default values. I like to try to keep all the configuration values stored in just one option field, so I prefer to put multiple variables into an array, and serialize them for storage in the database (update - wordpress handles the serializing/unserializing for you with the function maybe_serialize. Read more about it here.) [...]</description>
		<content:encoded><![CDATA[<p>[...] First, we get the option we&#8217;re going to use to store the configuration infomation for this widget. If it doesnt exist (meaning that this is the first time the widget code has been run, so our plugin has likely just been installed), we&#8217;ll create it with some default values. I like to try to keep all the configuration values stored in just one option field, so I prefer to put multiple variables into an array, and serialize them for storage in the database (update &#8211; wordpress handles the serializing/unserializing for you with the function maybe_serialize. Read more about it here.) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
