O:9:"magpierss":19:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:10:{i:0;a:12:{s:5:"title";s:43:"WordPress 2.1.1 dangerous, Upgrade to 2.1.2";s:4:"link";s:53:"http://wordpress.org/development/2007/03/upgrade-212/";s:8:"comments";s:62:"http://wordpress.org/development/2007/03/upgrade-212/#comments";s:7:"pubdate";s:31:"Fri, 02 Mar 2007 21:53:18 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:8:"Releases";s:4:"guid";s:53:"http://wordpress.org/development/2007/03/upgrade-212/";s:11:"description";s:343:"Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.
Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code [...]";s:7:"content";a:1:{s:7:"encoded";s:660:"<p>Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.</p>
<p>Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that the 2.1.1 download had been modified from its original code. We took the website down immediately to investigate what happened.</p>
<p> <a href="http://wordpress.org/development/2007/03/upgrade-212/#more-199" class="more-link">(more&#8230;)</a></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:58:"http://wordpress.org/development/2007/03/upgrade-212/feed/";}s:7:"summary";s:343:"Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.
Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code [...]";s:12:"atom_content";s:660:"<p>Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.</p>
<p>Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that the 2.1.1 download had been modified from its original code. We took the website down immediately to investigate what happened.</p>
<p> <a href="http://wordpress.org/development/2007/03/upgrade-212/#more-199" class="more-link">(more&#8230;)</a></p>
";}i:1;a:12:{s:5:"title";s:29:"New Releases: 2.1.1 and 2.0.9";s:4:"link";s:54:"http://wordpress.org/development/2007/02/new-releases/";s:8:"comments";s:63:"http://wordpress.org/development/2007/02/new-releases/#comments";s:7:"pubdate";s:31:"Wed, 21 Feb 2007 06:45:12 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:8:"Releases";s:4:"guid";s:54:"http://wordpress.org/development/2007/02/new-releases/";s:11:"description";s:369:"We&#8217;ve got a new bugfix and security release for both of our actively maintained branches of WordPress. Version 2.1.1 includes about 30 bug fixes, mostly minor things around encoding, XML-RPC, the object cache, and HTML code. It&#8217;s available for immediate download on our download page. 
Version 2.0.9 only includes the security update, which was around [...]";s:7:"content";a:1:{s:7:"encoded";s:991:"<p>We&#8217;ve got a new bugfix and security release for both of our actively maintained branches of WordPress. Version 2.1.1 includes about 30 bug fixes, mostly minor things around encoding, XML-RPC, the object cache, and HTML code. It&#8217;s available <a href="http://wordpress.org/download/">for immediate download on our download page</a>. </p>
<p>Version 2.0.9 only includes the security update, which was around the code we use to prevent XSS. You can download it from <a href="http://wordpress.org/download/release-archive/">our release archive</a>. As a reminder, we&#8217;ve committed to proving security updates to 2.0 through 2010, but all new features and development are going into the newer branch, which is at this time 2.1.</p>
<p>This is a low-to-medium priority update recommended for all WordPress users. After the break is a list of changed files.</p>
<p> <a href="http://wordpress.org/development/2007/02/new-releases/#more-197" class="more-link">(more&#8230;)</a></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:59:"http://wordpress.org/development/2007/02/new-releases/feed/";}s:7:"summary";s:369:"We&#8217;ve got a new bugfix and security release for both of our actively maintained branches of WordPress. Version 2.1.1 includes about 30 bug fixes, mostly minor things around encoding, XML-RPC, the object cache, and HTML code. It&#8217;s available for immediate download on our download page. 
Version 2.0.9 only includes the security update, which was around [...]";s:12:"atom_content";s:991:"<p>We&#8217;ve got a new bugfix and security release for both of our actively maintained branches of WordPress. Version 2.1.1 includes about 30 bug fixes, mostly minor things around encoding, XML-RPC, the object cache, and HTML code. It&#8217;s available <a href="http://wordpress.org/download/">for immediate download on our download page</a>. </p>
<p>Version 2.0.9 only includes the security update, which was around the code we use to prevent XSS. You can download it from <a href="http://wordpress.org/download/release-archive/">our release archive</a>. As a reminder, we&#8217;ve committed to proving security updates to 2.0 through 2010, but all new features and development are going into the newer branch, which is at this time 2.1.</p>
<p>This is a low-to-medium priority update recommended for all WordPress users. After the break is a list of changed files.</p>
<p> <a href="http://wordpress.org/development/2007/02/new-releases/#more-197" class="more-link">(more&#8230;)</a></p>
";}i:2;a:12:{s:5:"title";s:18:"WordPress 2.1 Ella";s:4:"link";s:49:"http://wordpress.org/development/2007/01/ella-21/";s:8:"comments";s:58:"http://wordpress.org/development/2007/01/ella-21/#comments";s:7:"pubdate";s:31:"Mon, 22 Jan 2007 22:24:43 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:8:"Releases";s:4:"guid";s:49:"http://wordpress.org/development/2007/01/ella-21/";s:11:"description";s:377:"On behalf of the WordPress.org community of commiters, contributers, and volunteers, I&#8217;m very proud to announce the immediate availability of WordPress 2.1 &#8220;Ella&#8221;, named for jazz vocalist Ella Fitzgerald. Here&#8217;s a sampling of what&#8217;s in the new version:

 Autosave makes sure you never lose a post again. 
 Our new tabbed editor allows you to [...]";s:7:"content";a:1:{s:7:"encoded";s:4690:"<p>On behalf of the WordPress.org community of commiters, contributers, and volunteers, I&#8217;m very proud to announce <a href="http://wordpress.org/download/">the immediate availability of WordPress 2.1 &#8220;Ella&#8221;</a>, named for jazz vocalist <a href="http://www.ellafitzgerald.com/">Ella Fitzgerald</a>. Here&#8217;s a sampling of what&#8217;s in the new version:</p>
<ul>
<li> <strong>Autosave</strong> makes sure you never lose a post again. </li>
<li> Our new <strong>tabbed editor</strong> allows you to switch between WYSIWYG and code editing instantly while writing a post. </li>
<li> The <strong>lossless XML import and export</strong> makes it easy for you to move your content between WordPress blogs. </li>
<li> Our completely redone visual editor also now includes <strong>spell checking</strong>. </li>
<li> <strong>New search engine privacy option</strong> allows you take you to indicate your blog shouldn&#8217;t ping or be indexed by search engines like Google. </li>
<li> You can set any &#8220;page&#8221; to be the front page of your site, and put the latest posts somewhere else, making it much easier to use WordPress as a content management system. </li>
<li> Much more efficient database code, faster than previous versions. <a href="http://dammit.lt/">Domas Mituzas</a> from MySQL went over all our queries with a fine-toothed comb. </li>
<li> Links in your blogroll now support sub-categories and you can add categories on the fly. </li>
<li> Redesigned login screen from the Shuttle project. </li>
<li> More AJAX to make custom fields, moderation, deletions, and more all faster. My favorite is the comments page, which new lets you approve or unapprove things instantly. </li>
<li> Pages can now be drafts, or private. </li>
<li> Our admin has been refreshed to load faster and be more visually consistent. </li>
<li> The dashboard now loads instantly and brings RSS feeds asynchronously in the background. </li>
<li> Comment feeds now include all the comments, not just the last 10. </li>
<li> Better internationalization and support for right-to-left languages. </li>
<li> The <strong>upload manager</strong> lets you easily manage all your uploads pictures, video, and audio. </li>
<li> A <a href="http://akismet.com/blog/2007/01/version-20/">new version of the Akismet plugin</a> is bundled. </li>
</ul>
<p>&#8230;and much, much more. There are little easter eggs hidden everywhere, so the best way to find everything new is to <a href="http://wordpress.org/download/">just try it out</a>.</p>
<h3>Developer Features</h3>
<p>Developers will especially love this release, as it has much cleaner code than 2.0 and includes hundreds of enhancements that will enable a new generation of richer plugins. Here&#8217;s a taste of some of the things included:</p>
<ul>
<li> Psuedo-cron functionality let&#8217;s you schedule events much like cron. </li>
<li> Users admin can now comfortably handle hundreds of thousands of users. </li>
<li> The new WP_Error class cleans up how we do error reporting and handling. </li>
<li> The javascript loader makes it easier for plugins to include rich functionality. </li>
<li> Tons of new hooks and APIs. </li>
<li> We&#8217;ve started to fill out our code inline documentation. </li>
<li> Image and thumbnail API allows for richer media plugins. </li>
<li> Custom header, color picker, and image cropping framework. </li>
</ul>
<p>2.1 also <a href="http://trac.wordpress.org/query?status=closed&#038;milestone=2.1">includes over 550 bug fixes</a>.</p>
<h3>The Future</h3>
<p>What&#8217;s really exciting for me is what&#8217;s coming in the future. First of all, the 2.0 series was an unparalleled success, with over 1.8 million downloads, and thanks to the work of Mark Jaquith we&#8217;re committing to maintaining stable security and bug fixes on the 2.0 branch until 2010.</p>
<p>More exciting for most of our users, though, is our new development cycle. Based on everything we&#8217;ve learned in the past 3 years of doing WordPress, we&#8217;ve decided to shift to a more frequent release schedule like Ubuntu, with major releases coming several times a year. So, for the first time in WordPress&#8217; history, I have an answer to when the next version is coming out: April 23rd.</p>
<p>Even better, the development will be driven primarily by <a href="http://wordpress.org/extend/ideas/">the features you guys are voting for on the ideas board</a>. (But wait, there&#8217;s more: the ideas board now has a new Hot-or-Not-like interface for rating a bunch of ideas at once, <a href="http://wordpress.org/extend/ideas/view.php?view=not_voted">so go get your vote on and have a say in WordPress 2.2</a>.)</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:54:"http://wordpress.org/development/2007/01/ella-21/feed/";}s:7:"summary";s:377:"On behalf of the WordPress.org community of commiters, contributers, and volunteers, I&#8217;m very proud to announce the immediate availability of WordPress 2.1 &#8220;Ella&#8221;, named for jazz vocalist Ella Fitzgerald. Here&#8217;s a sampling of what&#8217;s in the new version:

 Autosave makes sure you never lose a post again. 
 Our new tabbed editor allows you to [...]";s:12:"atom_content";s:4690:"<p>On behalf of the WordPress.org community of commiters, contributers, and volunteers, I&#8217;m very proud to announce <a href="http://wordpress.org/download/">the immediate availability of WordPress 2.1 &#8220;Ella&#8221;</a>, named for jazz vocalist <a href="http://www.ellafitzgerald.com/">Ella Fitzgerald</a>. Here&#8217;s a sampling of what&#8217;s in the new version:</p>
<ul>
<li> <strong>Autosave</strong> makes sure you never lose a post again. </li>
<li> Our new <strong>tabbed editor</strong> allows you to switch between WYSIWYG and code editing instantly while writing a post. </li>
<li> The <strong>lossless XML import and export</strong> makes it easy for you to move your content between WordPress blogs. </li>
<li> Our completely redone visual editor also now includes <strong>spell checking</strong>. </li>
<li> <strong>New search engine privacy option</strong> allows you take you to indicate your blog shouldn&#8217;t ping or be indexed by search engines like Google. </li>
<li> You can set any &#8220;page&#8221; to be the front page of your site, and put the latest posts somewhere else, making it much easier to use WordPress as a content management system. </li>
<li> Much more efficient database code, faster than previous versions. <a href="http://dammit.lt/">Domas Mituzas</a> from MySQL went over all our queries with a fine-toothed comb. </li>
<li> Links in your blogroll now support sub-categories and you can add categories on the fly. </li>
<li> Redesigned login screen from the Shuttle project. </li>
<li> More AJAX to make custom fields, moderation, deletions, and more all faster. My favorite is the comments page, which new lets you approve or unapprove things instantly. </li>
<li> Pages can now be drafts, or private. </li>
<li> Our admin has been refreshed to load faster and be more visually consistent. </li>
<li> The dashboard now loads instantly and brings RSS feeds asynchronously in the background. </li>
<li> Comment feeds now include all the comments, not just the last 10. </li>
<li> Better internationalization and support for right-to-left languages. </li>
<li> The <strong>upload manager</strong> lets you easily manage all your uploads pictures, video, and audio. </li>
<li> A <a href="http://akismet.com/blog/2007/01/version-20/">new version of the Akismet plugin</a> is bundled. </li>
</ul>
<p>&#8230;and much, much more. There are little easter eggs hidden everywhere, so the best way to find everything new is to <a href="http://wordpress.org/download/">just try it out</a>.</p>
<h3>Developer Features</h3>
<p>Developers will especially love this release, as it has much cleaner code than 2.0 and includes hundreds of enhancements that will enable a new generation of richer plugins. Here&#8217;s a taste of some of the things included:</p>
<ul>
<li> Psuedo-cron functionality let&#8217;s you schedule events much like cron. </li>
<li> Users admin can now comfortably handle hundreds of thousands of users. </li>
<li> The new WP_Error class cleans up how we do error reporting and handling. </li>
<li> The javascript loader makes it easier for plugins to include rich functionality. </li>
<li> Tons of new hooks and APIs. </li>
<li> We&#8217;ve started to fill out our code inline documentation. </li>
<li> Image and thumbnail API allows for richer media plugins. </li>
<li> Custom header, color picker, and image cropping framework. </li>
</ul>
<p>2.1 also <a href="http://trac.wordpress.org/query?status=closed&#038;milestone=2.1">includes over 550 bug fixes</a>.</p>
<h3>The Future</h3>
<p>What&#8217;s really exciting for me is what&#8217;s coming in the future. First of all, the 2.0 series was an unparalleled success, with over 1.8 million downloads, and thanks to the work of Mark Jaquith we&#8217;re committing to maintaining stable security and bug fixes on the 2.0 branch until 2010.</p>
<p>More exciting for most of our users, though, is our new development cycle. Based on everything we&#8217;ve learned in the past 3 years of doing WordPress, we&#8217;ve decided to shift to a more frequent release schedule like Ubuntu, with major releases coming several times a year. So, for the first time in WordPress&#8217; history, I have an answer to when the next version is coming out: April 23rd.</p>
<p>Even better, the development will be driven primarily by <a href="http://wordpress.org/extend/ideas/">the features you guys are voting for on the ideas board</a>. (But wait, there&#8217;s more: the ideas board now has a new Hot-or-Not-like interface for rating a bunch of ideas at once, <a href="http://wordpress.org/extend/ideas/view.php?view=not_voted">so go get your vote on and have a say in WordPress 2.2</a>.)</p>
";}i:3;a:12:{s:5:"title";s:15:"WordPress 2.0.7";s:4:"link";s:55:"http://wordpress.org/development/2007/01/wordpress-207/";s:8:"comments";s:64:"http://wordpress.org/development/2007/01/wordpress-207/#comments";s:7:"pubdate";s:31:"Mon, 15 Jan 2007 22:14:24 +0000";s:2:"dc";a:1:{s:7:"creator";s:12:"Mark Jaquith";}s:8:"category";s:16:"SecurityReleases";s:4:"guid";s:55:"http://wordpress.org/development/2007/01/wordpress-207/";s:11:"description";s:331:"Recently a bug in certain versions of PHP came to our attention that could cause a security vulnerability in your blog. We&#8217;re able to work around it fairly easily, so we&#8217;ve decided to release 2.0.7 to fix the PHP security problem and the Feedburner issue that was in 2.0.6. It is recommended that everyone running [...]";s:7:"content";a:1:{s:7:"encoded";s:2239:"<p>Recently a bug in certain versions of PHP came to our attention that could cause a security vulnerability in your blog. We&#8217;re able to work around it fairly easily, so we&#8217;ve decided to release 2.0.7 to fix the PHP security problem and the Feedburner issue that was in 2.0.6. It is recommended that everyone running WordPress 2.0.6 or lower <a href="http://wordpress.org/download/">upgrade to this new version</a>.</p>
<p>Because this is a much smaller update than previous versions, you do not have to update all of WordPress&#8217; files if you&#8217;re upgrading from version 2.0.6.  Here is the list of files that have changed since 2.0.6:</p>
<ul>
<li>wp-admin/inline-uploading.php</li>
<li>wp-admin/post.php</li>
<li>wp-includes/classes.php</li>
<li>wp-includes/functions.php</li>
<li>wp-settings.php</li>
<li>wp-includes/version.php</li>
</ul>
<p>We know it sucks to have a release only 10 days after our last one, but we think it&#8217;s important enough for your blog to be secure to do it, and hopefully only having to change a few files will make the upgrade easier than normal.</p>
<p>Here are the changes that have been made since 2.0.6:</p>
<ul>
<li>Security fix for <code>wp_unregister_GLOBALS()</code> to work around the <a href="http://www.hardened-php.net/hphp/zend_hash_del_key_or_index_vulnerability.html">zend_hash_del_key_or_index bug</a> in PHP 4 versions less than 4.4.3 and PHP 5 versions less than 5.1.4 with <code>register_globals</code> set to &#8220;On.&#8221;</li>
<li>Feeds now properly serve <code>304 Not Modified</code> headers instead of mismatched 200/304 headers (a.k.a. the FeedBurner bug).</li>
<li>Backport of another <code>304 Not Modified</code> fix from WordPress 2.1</li>
<li>Deleting WordPress Pages no longer gives an &#8220;Are You Sure?&#8221; prompt.</li>
<li>After deleting a WordPress Page, you are now properly redirected to the Edit Pages screen.</li>
<li>Sending an image at original size in Internet Explorer no longer adds an incorrect &#8220;height&#8221; attribute.</li>
</ul>
<p>And just as a reminder, the next major version of WordPress (2.1) is due out by the end of the month, but the 2.0 branch of WordPress will continue to be maintained for several years.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2007/01/wordpress-207/feed/";}s:7:"summary";s:331:"Recently a bug in certain versions of PHP came to our attention that could cause a security vulnerability in your blog. We&#8217;re able to work around it fairly easily, so we&#8217;ve decided to release 2.0.7 to fix the PHP security problem and the Feedburner issue that was in 2.0.6. It is recommended that everyone running [...]";s:12:"atom_content";s:2239:"<p>Recently a bug in certain versions of PHP came to our attention that could cause a security vulnerability in your blog. We&#8217;re able to work around it fairly easily, so we&#8217;ve decided to release 2.0.7 to fix the PHP security problem and the Feedburner issue that was in 2.0.6. It is recommended that everyone running WordPress 2.0.6 or lower <a href="http://wordpress.org/download/">upgrade to this new version</a>.</p>
<p>Because this is a much smaller update than previous versions, you do not have to update all of WordPress&#8217; files if you&#8217;re upgrading from version 2.0.6.  Here is the list of files that have changed since 2.0.6:</p>
<ul>
<li>wp-admin/inline-uploading.php</li>
<li>wp-admin/post.php</li>
<li>wp-includes/classes.php</li>
<li>wp-includes/functions.php</li>
<li>wp-settings.php</li>
<li>wp-includes/version.php</li>
</ul>
<p>We know it sucks to have a release only 10 days after our last one, but we think it&#8217;s important enough for your blog to be secure to do it, and hopefully only having to change a few files will make the upgrade easier than normal.</p>
<p>Here are the changes that have been made since 2.0.6:</p>
<ul>
<li>Security fix for <code>wp_unregister_GLOBALS()</code> to work around the <a href="http://www.hardened-php.net/hphp/zend_hash_del_key_or_index_vulnerability.html">zend_hash_del_key_or_index bug</a> in PHP 4 versions less than 4.4.3 and PHP 5 versions less than 5.1.4 with <code>register_globals</code> set to &#8220;On.&#8221;</li>
<li>Feeds now properly serve <code>304 Not Modified</code> headers instead of mismatched 200/304 headers (a.k.a. the FeedBurner bug).</li>
<li>Backport of another <code>304 Not Modified</code> fix from WordPress 2.1</li>
<li>Deleting WordPress Pages no longer gives an &#8220;Are You Sure?&#8221; prompt.</li>
<li>After deleting a WordPress Page, you are now properly redirected to the Edit Pages screen.</li>
<li>Sending an image at original size in Internet Explorer no longer adds an incorrect &#8220;height&#8221; attribute.</li>
</ul>
<p>And just as a reminder, the next major version of WordPress (2.1) is due out by the end of the month, but the 2.0 branch of WordPress will continue to be maintained for several years.</p>
";}i:4;a:12:{s:5:"title";s:17:"Ideas and Kvetch!";s:4:"link";s:58:"http://wordpress.org/development/2007/01/ideas-and-kvetch/";s:8:"comments";s:67:"http://wordpress.org/development/2007/01/ideas-and-kvetch/#comments";s:7:"pubdate";s:31:"Tue, 09 Jan 2007 18:18:15 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:15:"MetaDevelopment";s:4:"guid";s:58:"http://wordpress.org/development/2007/01/ideas-and-kvetch/";s:11:"description";s:324:"It&#8217;s a new year, and we have a new major release of WordPress coming soon. (We&#8217;re currently aiming for the 22nd.) It&#8217;s as good a time as any to examine where we&#8217;ve been, and where we are, and where we&#8217;re going as a community. 2006 was a pretty exciting year, we saw 1.54 million downloads [...]";s:7:"content";a:1:{s:7:"encoded";s:2235:"<p>It&#8217;s a new year, and we have a new major release of WordPress coming soon. (We&#8217;re currently aiming for the 22nd.) It&#8217;s as good a time as any to examine where we&#8217;ve been, and where we are, and where we&#8217;re going as a community. 2006 was a pretty exciting year, we saw 1.54 million downloads of WP, and that&#8217;s not even counting the people who install it through their host&#8217;s one-click install or the half a million who have experienced it through the hosted WordPress.com. WordPress is touching more lives than ever.</p>
<p>However, just because what we&#8217;ve done has worked in the past doesn&#8217;t mean it&#8217;s the best for the future. We have to take a self-critical look at assumptions we have about our development process and WP itself. The upcoming release, which has been long coming, is a perfect time to focus on WP&#8217;s secret ingredient&#8230; you.</p>
<p>If you could add anything in the world to WordPress, what would it be? If you could name the thing that frustrates you the most about WP, what would that be?</p>
<p>Now you can tell us. We&#8217;re announcing new projects&#8212;two sides of the same coin.</p>
<p><a href="http://wordpress.org/extend/ideas/">The first is simply called Ideas</a>, and it&#8217;s a place where you can share your wildest WordPress wishes with the world, and also vote on other people&#8217;s ideas. This allows people outside our normal circle of developers to have a direct say in what goes into the next version of WordPress. For 2.2, which comes out in late April, we will include the top voted on features, so propose something, tell your friends about it, and link it from your blog.</p>
<p>The second we&#8217;ve named after the <a href="http://www.answers.com/kvetch">Yiddish word</a>, <a href="http://wordpress.org/extend/kvetch/">Kvetch</a>. This is a place where you can quickly and anonymously express whatever might disagree with you in the WordPress world. Let it all loose, but try to keep it PG rated, and we&#8217;ll show a random kvetch on the page once we get enough in the system.</p>
<p>Both are just part of putting you guys&#8212;our users&#8212;first. It&#8217;s easy because there&#8217;s so many of you.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:63:"http://wordpress.org/development/2007/01/ideas-and-kvetch/feed/";}s:7:"summary";s:324:"It&#8217;s a new year, and we have a new major release of WordPress coming soon. (We&#8217;re currently aiming for the 22nd.) It&#8217;s as good a time as any to examine where we&#8217;ve been, and where we are, and where we&#8217;re going as a community. 2006 was a pretty exciting year, we saw 1.54 million downloads [...]";s:12:"atom_content";s:2235:"<p>It&#8217;s a new year, and we have a new major release of WordPress coming soon. (We&#8217;re currently aiming for the 22nd.) It&#8217;s as good a time as any to examine where we&#8217;ve been, and where we are, and where we&#8217;re going as a community. 2006 was a pretty exciting year, we saw 1.54 million downloads of WP, and that&#8217;s not even counting the people who install it through their host&#8217;s one-click install or the half a million who have experienced it through the hosted WordPress.com. WordPress is touching more lives than ever.</p>
<p>However, just because what we&#8217;ve done has worked in the past doesn&#8217;t mean it&#8217;s the best for the future. We have to take a self-critical look at assumptions we have about our development process and WP itself. The upcoming release, which has been long coming, is a perfect time to focus on WP&#8217;s secret ingredient&#8230; you.</p>
<p>If you could add anything in the world to WordPress, what would it be? If you could name the thing that frustrates you the most about WP, what would that be?</p>
<p>Now you can tell us. We&#8217;re announcing new projects&#8212;two sides of the same coin.</p>
<p><a href="http://wordpress.org/extend/ideas/">The first is simply called Ideas</a>, and it&#8217;s a place where you can share your wildest WordPress wishes with the world, and also vote on other people&#8217;s ideas. This allows people outside our normal circle of developers to have a direct say in what goes into the next version of WordPress. For 2.2, which comes out in late April, we will include the top voted on features, so propose something, tell your friends about it, and link it from your blog.</p>
<p>The second we&#8217;ve named after the <a href="http://www.answers.com/kvetch">Yiddish word</a>, <a href="http://wordpress.org/extend/kvetch/">Kvetch</a>. This is a place where you can quickly and anonymously express whatever might disagree with you in the WordPress world. Let it all loose, but try to keep it PG rated, and we&#8217;ll show a random kvetch on the page once we get enough in the system.</p>
<p>Both are just part of putting you guys&#8212;our users&#8212;first. It&#8217;s easy because there&#8217;s so many of you.</p>
";}i:5;a:12:{s:5:"title";s:15:"WordPress 2.0.6";s:4:"link";s:55:"http://wordpress.org/development/2007/01/wordpress-206/";s:8:"comments";s:64:"http://wordpress.org/development/2007/01/wordpress-206/#comments";s:7:"pubdate";s:31:"Fri, 05 Jan 2007 13:24:14 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:16:"SecurityReleases";s:4:"guid";s:55:"http://wordpress.org/development/2007/01/wordpress-206/";s:11:"description";s:414:"We have a pretty important release available for everyone, it includes an important security fix and it&#8217;s recommended that everyone upgrade. This is the latest release in our stable 2.0 line, which we&#8217;ve committed to maintaining for several more years.
Here&#8217;s what&#8217;s new:

The aforementioned security fixes.
HTML quicktags now work in Safari browsers.
Comments are filtered to prevent [...]";s:7:"content";a:1:{s:7:"encoded";s:1444:"<p>We have a pretty important release available for everyone, it includes an important security fix and it&#8217;s recommended that everyone upgrade. This is the latest release in our stable 2.0 line, which we&#8217;ve committed to maintaining for several more years.</p>
<p>Here&#8217;s what&#8217;s new:</p>
<ul>
<li>The aforementioned security fixes.</li>
<li>HTML quicktags now work in Safari browsers.</li>
<li>Comments are filtered to prevent them from messing up your blog layout.</li>
<li>Compatibility with PHP/FastCGI setups.</li>
</ul>
<p>For developers, there&#8217;s a new anti-XSS function called attribute_escape(), and a new filter called &#8220;query&#8221; which allows you filter any SQL at runtime. (Which is pretty powerful.) Thanks to Mark Jaquith  for handling this release and Stefan Esser for responsibly reporting the security issue.</p>
<p>As always, <a href="http://wordpress.org/download/">you can download the latest version of WordPress here</a>.</p>
<p>As a side note, this is probably our last release before 2.1 is out, which will be our first major feature release in quite a while. 2.1 just entered beta stage, so if you&#8217;re interested in helping out with that process consider <a href="http://wordpress.org/download/beta/">joining our beta group</a>. As a reminder, if you&#8217;re a plugin or theme author you should check your code to make sure it&#8217;s compatible with 2.1 before the release.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2007/01/wordpress-206/feed/";}s:7:"summary";s:414:"We have a pretty important release available for everyone, it includes an important security fix and it&#8217;s recommended that everyone upgrade. This is the latest release in our stable 2.0 line, which we&#8217;ve committed to maintaining for several more years.
Here&#8217;s what&#8217;s new:

The aforementioned security fixes.
HTML quicktags now work in Safari browsers.
Comments are filtered to prevent [...]";s:12:"atom_content";s:1444:"<p>We have a pretty important release available for everyone, it includes an important security fix and it&#8217;s recommended that everyone upgrade. This is the latest release in our stable 2.0 line, which we&#8217;ve committed to maintaining for several more years.</p>
<p>Here&#8217;s what&#8217;s new:</p>
<ul>
<li>The aforementioned security fixes.</li>
<li>HTML quicktags now work in Safari browsers.</li>
<li>Comments are filtered to prevent them from messing up your blog layout.</li>
<li>Compatibility with PHP/FastCGI setups.</li>
</ul>
<p>For developers, there&#8217;s a new anti-XSS function called attribute_escape(), and a new filter called &#8220;query&#8221; which allows you filter any SQL at runtime. (Which is pretty powerful.) Thanks to Mark Jaquith  for handling this release and Stefan Esser for responsibly reporting the security issue.</p>
<p>As always, <a href="http://wordpress.org/download/">you can download the latest version of WordPress here</a>.</p>
<p>As a side note, this is probably our last release before 2.1 is out, which will be our first major feature release in quite a while. 2.1 just entered beta stage, so if you&#8217;re interested in helping out with that process consider <a href="http://wordpress.org/download/beta/">joining our beta group</a>. As a reminder, if you&#8217;re a plugin or theme author you should check your code to make sure it&#8217;s compatible with 2.1 before the release.</p>
";}i:6;a:12:{s:5:"title";s:16:"Limited T-shirts";s:4:"link";s:58:"http://wordpress.org/development/2006/12/limited-t-shirts/";s:8:"comments";s:67:"http://wordpress.org/development/2006/12/limited-t-shirts/#comments";s:7:"pubdate";s:31:"Thu, 14 Dec 2006 23:49:02 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:13:"StoreWordCamp";s:4:"guid";s:58:"http://wordpress.org/development/2006/12/limited-t-shirts/";s:11:"description";s:306:"At various events throughout 2006, like SxSW and WordCamp we had t-shirts and each time we got a ton of requests for people who weren&#8217;t there to be able to buy them. Well, now you can. We have a limited supply of some of our shirts from this year available to order online.
You can&#8217;t tell [...]";s:7:"content";a:1:{s:7:"encoded";s:1430:"<p>At various events throughout 2006, like SxSW and WordCamp we had t-shirts and each time we got a ton of requests for people who weren&#8217;t there to be able to buy them. Well, now you can. We have a limited supply of some of our shirts from this year <a href="http://www.goodstorm.com/stores/wordpress">available to order online</a>.</p>
<p>You can&#8217;t tell from the pictures, but the black shirts have a larger W logo and make you feel a bit <a href="http://flickr.com/photos/photomatt/110143508/">like Superman</a>. The grey WordCamp shirts have the logo a bit smaller, and are a bit reminiscent of <a href="http://daringfireball.net/">Daring Fireball</a>. Both look good with jeans.</p>
<p>Part of the idea is once we print a style, we never do it again, so each shirt will be representative of a certain time in WordPress history. Since these are the very first, they make a great gift for yourself or that special blogging geek in you life. <a href="http://www.goodstorm.com/stores/wordpress">Check out the store</a>.</p>
<p>If you have any pictures of yourself in a WordPress shirt on Flickr, be sure to <a href="http://flickr.com/photos/tags/wordpressshirt/">tag them wordpressshirt</a> to join the fun.</p>
<p><strong>Update:</strong> We&#8217;re very sorry, but Goodstorm only ships to the US. If you&#8217;d like that to change, <a href="http://www.goodstorm.com/feedback">send Goodstorm some feedback</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:63:"http://wordpress.org/development/2006/12/limited-t-shirts/feed/";}s:7:"summary";s:306:"At various events throughout 2006, like SxSW and WordCamp we had t-shirts and each time we got a ton of requests for people who weren&#8217;t there to be able to buy them. Well, now you can. We have a limited supply of some of our shirts from this year available to order online.
You can&#8217;t tell [...]";s:12:"atom_content";s:1430:"<p>At various events throughout 2006, like SxSW and WordCamp we had t-shirts and each time we got a ton of requests for people who weren&#8217;t there to be able to buy them. Well, now you can. We have a limited supply of some of our shirts from this year <a href="http://www.goodstorm.com/stores/wordpress">available to order online</a>.</p>
<p>You can&#8217;t tell from the pictures, but the black shirts have a larger W logo and make you feel a bit <a href="http://flickr.com/photos/photomatt/110143508/">like Superman</a>. The grey WordCamp shirts have the logo a bit smaller, and are a bit reminiscent of <a href="http://daringfireball.net/">Daring Fireball</a>. Both look good with jeans.</p>
<p>Part of the idea is once we print a style, we never do it again, so each shirt will be representative of a certain time in WordPress history. Since these are the very first, they make a great gift for yourself or that special blogging geek in you life. <a href="http://www.goodstorm.com/stores/wordpress">Check out the store</a>.</p>
<p>If you have any pictures of yourself in a WordPress shirt on Flickr, be sure to <a href="http://flickr.com/photos/tags/wordpressshirt/">tag them wordpressshirt</a> to join the fun.</p>
<p><strong>Update:</strong> We&#8217;re very sorry, but Goodstorm only ships to the US. If you&#8217;d like that to change, <a href="http://www.goodstorm.com/feedback">send Goodstorm some feedback</a>.</p>
";}i:7;a:12:{s:5:"title";s:31:"Is your plugin Naughty or Nice?";s:4:"link";s:57:"http://wordpress.org/development/2006/12/naughty-or-nice/";s:8:"comments";s:66:"http://wordpress.org/development/2006/12/naughty-or-nice/#comments";s:7:"pubdate";s:31:"Mon, 11 Dec 2006 18:11:05 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:11:"Development";s:4:"guid";s:57:"http://wordpress.org/development/2006/12/naughty-or-nice/";s:11:"description";s:315:"Guest article by Aaron Brazell
WordPress 2.1 is almost here and you know what that means for developers. It’s time to pull out those old plugins you’ve had stashed, blow off the dust and start applying some spit and polish and make sure it will last longer than Grandma’s Ham and Bean soup that has been [...]";s:7:"content";a:1:{s:7:"encoded";s:2284:"<p><cite>Guest article by <a href='http://www.technosailor.com/'>Aaron Brazell</a></cite></p>
<p>WordPress 2.1 is almost here and you know what that means for developers. It’s time to pull out those old plugins you’ve had stashed, blow off the dust and start applying some spit and polish and make sure it will last longer than Grandma’s Ham and Bean soup that has been sitting in the refrigerator for weeks.</p>
<p>Many of the big changes in WordPress 2.1 are MySQL related so grab a pen and paper (or open Notepad) and start taking notes.</p>
<ul>
<li>The <code>$table*</code> variables have all been eliminated. They have not been deprecated as doing so would mean that the variables are still present but developers are no longer encouraged to use them. In this case, they have been removed from the core. When you&#8217;re developing plugins that contain SQL statements, ensure you globalize <code>$wpdb</code>, and call tables using <code>$wpdb->posts</code>, <code>$wpdb->post2cat</code>, etc. Likewise, the former <code>$table_prefix</code> variable that developers could globalize before to find the MySQL table prefix defined in <code>wp-config.php</code> has also been deprecated in favor of <code>$wpdb->prefix</code>.</li>
<li>Developers using the former linkcategories table should be aware that link categories are now part of categories. They are simply given another category ID and are not maintained separate from post categories.</li>
<li>The posts table now has a column of <code>post_type</code> that should help developers distinguish between posts and pages.</li>
<li>Future posts now gain the <code>post_status</code> of &#8216;future&#8217; which eliminates the use of <code>NOW()</code> in all queries in the core. Plugin developers should follow suit.</li>
</ul>
<p>WordPress 2.1 is nearing the time when the codebase will be released for testing, but it&#8217;s not too early to get those plugins and themes tweaked for the release. There is a <a href="http://codex.wordpress.org/User:Spencerp/2.1alpha3_Plugin_Compatibility">Codex page</a> where plugin compatibility is being tracked as well.</p>
<p><strong>Editor&#8217;s note:</strong> If you stick to the WP APIs as much as possible you won&#8217;t run into plugin upgrade issues like this.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:62:"http://wordpress.org/development/2006/12/naughty-or-nice/feed/";}s:7:"summary";s:315:"Guest article by Aaron Brazell
WordPress 2.1 is almost here and you know what that means for developers. It’s time to pull out those old plugins you’ve had stashed, blow off the dust and start applying some spit and polish and make sure it will last longer than Grandma’s Ham and Bean soup that has been [...]";s:12:"atom_content";s:2284:"<p><cite>Guest article by <a href='http://www.technosailor.com/'>Aaron Brazell</a></cite></p>
<p>WordPress 2.1 is almost here and you know what that means for developers. It’s time to pull out those old plugins you’ve had stashed, blow off the dust and start applying some spit and polish and make sure it will last longer than Grandma’s Ham and Bean soup that has been sitting in the refrigerator for weeks.</p>
<p>Many of the big changes in WordPress 2.1 are MySQL related so grab a pen and paper (or open Notepad) and start taking notes.</p>
<ul>
<li>The <code>$table*</code> variables have all been eliminated. They have not been deprecated as doing so would mean that the variables are still present but developers are no longer encouraged to use them. In this case, they have been removed from the core. When you&#8217;re developing plugins that contain SQL statements, ensure you globalize <code>$wpdb</code>, and call tables using <code>$wpdb->posts</code>, <code>$wpdb->post2cat</code>, etc. Likewise, the former <code>$table_prefix</code> variable that developers could globalize before to find the MySQL table prefix defined in <code>wp-config.php</code> has also been deprecated in favor of <code>$wpdb->prefix</code>.</li>
<li>Developers using the former linkcategories table should be aware that link categories are now part of categories. They are simply given another category ID and are not maintained separate from post categories.</li>
<li>The posts table now has a column of <code>post_type</code> that should help developers distinguish between posts and pages.</li>
<li>Future posts now gain the <code>post_status</code> of &#8216;future&#8217; which eliminates the use of <code>NOW()</code> in all queries in the core. Plugin developers should follow suit.</li>
</ul>
<p>WordPress 2.1 is nearing the time when the codebase will be released for testing, but it&#8217;s not too early to get those plugins and themes tweaked for the release. There is a <a href="http://codex.wordpress.org/User:Spencerp/2.1alpha3_Plugin_Compatibility">Codex page</a> where plugin compatibility is being tracked as well.</p>
<p><strong>Editor&#8217;s note:</strong> If you stick to the WP APIs as much as possible you won&#8217;t run into plugin upgrade issues like this.</p>
";}i:8;a:12:{s:5:"title";s:23:"WordPress 2.0.5 - Ronan";s:4:"link";s:51:"http://wordpress.org/development/2006/10/205-ronan/";s:8:"comments";s:60:"http://wordpress.org/development/2006/10/205-ronan/#comments";s:7:"pubdate";s:31:"Fri, 27 Oct 2006 23:17:01 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:8:"Releases";s:4:"guid";s:51:"http://wordpress.org/development/2006/10/205-ronan/";s:11:"description";s:360:"It&#8217;s new release time. The latest in our venerable 2.0 series, which now counts over 1.2 million downloads, is available for download immediately, and we suggest everyone upgrade as this includes security fixes. We&#8217;re breaking the tradition of naming releases after jazz musicians to congratulate Ryan Boren on his new son (and first WP baby) [...]";s:7:"content";a:1:{s:7:"encoded";s:1327:"<p>It&#8217;s new release time. The latest in our venerable 2.0 series, which now counts over 1.2 million downloads, <a href="http://wordpress.org/download/">is available for download immediately</a>, and we suggest everyone upgrade as this includes security fixes. We&#8217;re breaking the tradition of naming releases after jazz musicians to congratulate Ryan Boren on his new son (and first WP baby) Ronan.</p>
<p>What&#8217;s new? We have about 50 or so bugfixes, which you <a href="http://trac.wordpress.org/query?status=closed&amp;resolution=fixed&amp;milestone=2.0.5">can review on our dev tracker here</a>, mostly minor bug fixes around feeds, custom fields, and internationalization. If you&#8217;d like a nitty-gritty view, check out <a href="http://markjaquith.wordpress.com/2006/10/17/changes-in-wordpress-205/">Mark&#8217;s blog post on the changes</a>.</p>
<p>Like every release this was the result of a lot of people in the WordPress community, and I&#8217;d like to thank all our contributors and testers including Mustlive, Peter Westwood, and Robert Deaton. This is also the first release handled by our new 2.0 maintainer, Mark Jaquith. He joins myself and Ryan with commit access and is &#8220;committed&#8221; to keeping the 2.0 base stable as we head into the exciting new 2.1 world. Congrats to Mark</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:56:"http://wordpress.org/development/2006/10/205-ronan/feed/";}s:7:"summary";s:360:"It&#8217;s new release time. The latest in our venerable 2.0 series, which now counts over 1.2 million downloads, is available for download immediately, and we suggest everyone upgrade as this includes security fixes. We&#8217;re breaking the tradition of naming releases after jazz musicians to congratulate Ryan Boren on his new son (and first WP baby) [...]";s:12:"atom_content";s:1327:"<p>It&#8217;s new release time. The latest in our venerable 2.0 series, which now counts over 1.2 million downloads, <a href="http://wordpress.org/download/">is available for download immediately</a>, and we suggest everyone upgrade as this includes security fixes. We&#8217;re breaking the tradition of naming releases after jazz musicians to congratulate Ryan Boren on his new son (and first WP baby) Ronan.</p>
<p>What&#8217;s new? We have about 50 or so bugfixes, which you <a href="http://trac.wordpress.org/query?status=closed&amp;resolution=fixed&amp;milestone=2.0.5">can review on our dev tracker here</a>, mostly minor bug fixes around feeds, custom fields, and internationalization. If you&#8217;d like a nitty-gritty view, check out <a href="http://markjaquith.wordpress.com/2006/10/17/changes-in-wordpress-205/">Mark&#8217;s blog post on the changes</a>.</p>
<p>Like every release this was the result of a lot of people in the WordPress community, and I&#8217;d like to thank all our contributors and testers including Mustlive, Peter Westwood, and Robert Deaton. This is also the first release handled by our new 2.0 maintainer, Mark Jaquith. He joins myself and Ryan with commit access and is &#8220;committed&#8221; to keeping the 2.0 base stable as we head into the exciting new 2.1 world. Congrats to Mark</p>
";}i:9;a:12:{s:5:"title";s:18:"MU 1.0 and bbPress";s:4:"link";s:56:"http://wordpress.org/development/2006/10/mu-and-bbpress/";s:8:"comments";s:65:"http://wordpress.org/development/2006/10/mu-and-bbpress/#comments";s:7:"pubdate";s:31:"Mon, 23 Oct 2006 09:54:24 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:26:"GeneralReleasesDevelopment";s:4:"guid";s:56:"http://wordpress.org/development/2006/10/mu-and-bbpress/";s:11:"description";s:349:"The WordPress family has been really starting to grow lately. I wanted to let you guys know about two big releases: WordPress Multi-user 1.0 and bbPress 0.72.
WordPress MU is an official branch of WordPress that is designed for managing and hosting thousands of blogs instead of just one. It&#8217;s the software that powers WordPress.com, for [...]";s:7:"content";a:1:{s:7:"encoded";s:1846:"<p>The WordPress family has been really starting to grow lately. I wanted to let you guys know about two big releases: WordPress Multi-user 1.0 and bbPress 0.72.</p>
<p><a href="http://mu.wordpress.org/">WordPress MU</a> is an official branch of WordPress that is designed for managing and hosting thousands of blogs instead of just one. It&#8217;s the software that powers <a href="http://wordpress.com/">WordPress.com</a>, for example. MU has been in heavy development for about a year now, and we&#8217;ve finally polished it up to a place where we feel like it&#8217;s ready for public consumption. Since setup is a bit more complex than the 5-minute install of regular WordPress, MU is best suited for a more server-savvy audience. You can <a href="http://mu.wordpress.org/download/">download it on the WordPress MU site</a>. </p>
<p>Second I wanted to introduce an old friend you are all probably familiar with from our support forums, <a href="http://bbpress.org/">bbPress</a>. bbPress is forum software with the WordPress touch, and developed by the same folks. It has some pretty cool features, such as tagging, RSS feeds, Akismet spam protection, AJAX interaction, but the team focused the most on creating something fast and light. bbPress can power a forum with hundreds of thousands of posts with just a fraction of the load as WordPress. (If we could re-write WP from scratch, it would be a lot like bbPress.) What is probably most compelling for WordPress users, though, is that bbPress supports complete user and login integration with WP.</p>
<p>bbPress is not quite 1.0 yet, some of you may recognize the 0.72 version number from the early days of WordPress, but if you&#8217;re searching for a little something fresh in forum software, try <a href="http://bbpress.org/download/">downloading bbPress</a> and giving it a go.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:61:"http://wordpress.org/development/2006/10/mu-and-bbpress/feed/";}s:7:"summary";s:349:"The WordPress family has been really starting to grow lately. I wanted to let you guys know about two big releases: WordPress Multi-user 1.0 and bbPress 0.72.
WordPress MU is an official branch of WordPress that is designed for managing and hosting thousands of blogs instead of just one. It&#8217;s the software that powers WordPress.com, for [...]";s:12:"atom_content";s:1846:"<p>The WordPress family has been really starting to grow lately. I wanted to let you guys know about two big releases: WordPress Multi-user 1.0 and bbPress 0.72.</p>
<p><a href="http://mu.wordpress.org/">WordPress MU</a> is an official branch of WordPress that is designed for managing and hosting thousands of blogs instead of just one. It&#8217;s the software that powers <a href="http://wordpress.com/">WordPress.com</a>, for example. MU has been in heavy development for about a year now, and we&#8217;ve finally polished it up to a place where we feel like it&#8217;s ready for public consumption. Since setup is a bit more complex than the 5-minute install of regular WordPress, MU is best suited for a more server-savvy audience. You can <a href="http://mu.wordpress.org/download/">download it on the WordPress MU site</a>. </p>
<p>Second I wanted to introduce an old friend you are all probably familiar with from our support forums, <a href="http://bbpress.org/">bbPress</a>. bbPress is forum software with the WordPress touch, and developed by the same folks. It has some pretty cool features, such as tagging, RSS feeds, Akismet spam protection, AJAX interaction, but the team focused the most on creating something fast and light. bbPress can power a forum with hundreds of thousands of posts with just a fraction of the load as WordPress. (If we could re-write WP from scratch, it would be a lot like bbPress.) What is probably most compelling for WordPress users, though, is that bbPress supports complete user and login integration with WP.</p>
<p>bbPress is not quite 1.0 yet, some of you may recognize the 0.72 version number from the early days of WordPress, but if you&#8217;re searching for a little something fresh in forum software, try <a href="http://bbpress.org/download/">downloading bbPress</a> and giving it a go.</p>
";}}s:7:"channel";a:7:{s:5:"title";s:26:"WordPress Development Blog";s:4:"link";s:32:"http://wordpress.org/development";s:11:"description";s:33:"WordPress development and updates";s:7:"pubdate";s:31:"Fri, 02 Mar 2007 22:14:58 +0000";s:9:"generator";s:36:"http://wordpress.org/?v=2.2-bleeding";s:8:"language";s:2:"en";s:7:"tagline";s:33:"WordPress development and updates";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}s:13:"last_modified";s:31:"Fri, 02 Mar 2007 22:14:58 GMT
";s:4:"etag";s:36:""bcc4c67e16e019511fb753ae15aa3a6e"
";}