<?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>Pressed Words &#187; backporting</title>
	<atom:link href="http://pressedwords.com/tag/backporting/feed/" rel="self" type="application/rss+xml" />
	<link>http://pressedwords.com</link>
	<description>News and commentary about all things WordPress</description>
	<lastBuildDate>Thu, 11 Jun 2009 03:54:22 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1</generator>
	<item>
		<title>Backporting WordPress Security Fixes</title>
		<link>http://pressedwords.com/backporting-wp-security-patches/</link>
		<comments>http://pressedwords.com/backporting-wp-security-patches/#comments</comments>
		<pubDate>Wed, 07 May 2008 03:14:29 +0000</pubDate>
		<dc:creator><![CDATA[Austin Matzko]]></dc:creator>
				<category><![CDATA[Asides]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[2.3.3]]></category>
		<category><![CDATA[backporting]]></category>

		<guid isPermaLink="false">http://pressedwords.com/?p=58</guid>
		<description><![CDATA[Alex Schleber so dislikes WordPress 2.5 that he&#8217;s worked out how to patch version 2.3.3 with 2.5&#8217;s security patches instead of upgrading. It&#8217;s an approach I would recommend against. For one thing, there&#8217;s a good chance that one won&#8217;t recognize all of the patches via changelogs, if for no other reason than that sometimes new [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Alex Schleber so dislikes WordPress 2.5 that he&#8217;s worked out <a href="http://businessmindhacks.com/post/wordpress-233-security-retro-fit">how to patch version 2.3.3 with 2.5&#8217;s security patches</a> instead of upgrading.  It&#8217;s an approach I would recommend against.  For one thing, there&#8217;s a good chance that one won&#8217;t recognize all of the patches via changelogs, if for no other reason than that sometimes new features&#8212;not just fixes&#8212;have obviated bugs.  Also, 2.5 introduced a number of features on the back-end that I would miss.</p>
<p>I am curious about his antipathy towards version 2.5, something he promises to blog about later. My guess is that it has to do with the design of the administrative back-end.  That just confirms my opinion that the WordPress admin should be template-able.  After all, no one ever decided not to upgrade WordPress because they didn&#8217;t like Kubrick. </p>
]]></content:encoded>
			<wfw:commentRss>http://pressedwords.com/backporting-wp-security-patches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/5 queries in 0.001 seconds using memcached
Object Caching 235/238 objects using memcached

 Served from: pressedwords.com @ 2026-04-03 18:00:28 by W3 Total Cache -->