<?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: Plugin and theme authors should force users to upgrade</title>
	<atom:link href="http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade/feed" rel="self" type="application/rss+xml" />
	<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade</link>
	<description>Life, Blogging, and WordPress</description>
	<lastBuildDate>Thu, 18 Mar 2010 05:19:06 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: TOEIC</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-181335</link>
		<dc:creator>TOEIC</dc:creator>
		<pubDate>Sun, 14 Mar 2010 11:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-181335</guid>
		<description>This could be a great idea but upgrading the wordpress all the time is not really handy</description>
		<content:encoded><![CDATA[<p>This could be a great idea but upgrading the wordpress all the time is not really handy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: macky</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-175561</link>
		<dc:creator>macky</dc:creator>
		<pubDate>Thu, 21 Jan 2010 12:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-175561</guid>
		<description>i would say a high light in the wordpress plugin page is ok it is like most of the blogger will not login in the back end but it can really help blogger to keep updated their blog</description>
		<content:encoded><![CDATA[<p>i would say a high light in the wordpress plugin page is ok it is like most of the blogger will not login in the back end but it can really help blogger to keep updated their blog</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-173366</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-173366</guid>
		<description>&lt;p class=&quot;note&quot;&gt;Deleted for being the stupidest comment Justin has read in some time, not actually reading through and understanding the ideas in the post before commenting, and, most importantly, wasting Justin&#039;s time.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p class="note">Deleted for being the stupidest comment Justin has read in some time, not actually reading through and understanding the ideas in the post before commenting, and, most importantly, wasting Justin&#8217;s time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Byron</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-172050</link>
		<dc:creator>Byron</dc:creator>
		<pubDate>Wed, 30 Dec 2009 03:51:26 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-172050</guid>
		<description>Fact is, WP 2.7 is just not safe.  I know the hard way :( .  It&#039;s a community service to require upgrades, especially when something like the &quot;hidden Admin&quot; vulnerability of 2.7 is brought to light.</description>
		<content:encoded><![CDATA[<p>Fact is, WP 2.7 is just not safe.  I know the hard way <img src='http://justintadlock.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  .  It&#8217;s a community service to require upgrades, especially when something like the &#8220;hidden Admin&#8221; vulnerability of 2.7 is brought to light.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: avsa adasi</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-171766</link>
		<dc:creator>avsa adasi</dc:creator>
		<pubDate>Mon, 28 Dec 2009 19:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-171766</guid>
		<description>I have no problem with forcing users to upgrade.</description>
		<content:encoded><![CDATA[<p>I have no problem with forcing users to upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: darila</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-166289</link>
		<dc:creator>darila</dc:creator>
		<pubDate>Thu, 03 Dec 2009 10:46:57 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-166289</guid>
		<description>My experience is: users (also me, when im lasy) upgrade when something breaks. So yuor point of backwards compatibility seems right. But i think that largest possible audience is better thing.

greeting darila</description>
		<content:encoded><![CDATA[<p>My experience is: users (also me, when im lasy) upgrade when something breaks. So yuor point of backwards compatibility seems right. But i think that largest possible audience is better thing.</p>
<p>greeting darila</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Hancock</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-165818</link>
		<dc:creator>Carl Hancock</dc:creator>
		<pubDate>Tue, 01 Dec 2009 06:13:41 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-165818</guid>
		<description>I have no problem with forcing users to upgrade.  

The fact of the matter is if you don&#039;t keep your WordPress install up to date you are leaving yourself vulnerable to being hacked.  Plain and simple.  One of the major features that WordPress brings with each new release is patching security holes.

If your plugins break every time you upgrade WordPress you are using the wrong plugins. Pick plugins by developers who actively maintain their plugin with each new WordPress release and you won&#039;t have that problem.

If you rely on plugins that aren&#039;t actively being maintained by their developer... all I can say is good luck with that.  You made your own bed.</description>
		<content:encoded><![CDATA[<p>I have no problem with forcing users to upgrade.  </p>
<p>The fact of the matter is if you don&#8217;t keep your WordPress install up to date you are leaving yourself vulnerable to being hacked.  Plain and simple.  One of the major features that WordPress brings with each new release is patching security holes.</p>
<p>If your plugins break every time you upgrade WordPress you are using the wrong plugins. Pick plugins by developers who actively maintain their plugin with each new WordPress release and you won&#8217;t have that problem.</p>
<p>If you rely on plugins that aren&#8217;t actively being maintained by their developer&#8230; all I can say is good luck with that.  You made your own bed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davidalees</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-165495</link>
		<dc:creator>Davidalees</dc:creator>
		<pubDate>Sun, 29 Nov 2009 13:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-165495</guid>
		<description>I agree with Justin. We all have to remmember that these plugins are usually FREE.</description>
		<content:encoded><![CDATA[<p>I agree with Justin. We all have to remmember that these plugins are usually FREE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arkenor</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-162878</link>
		<dc:creator>Arkenor</dc:creator>
		<pubDate>Tue, 17 Nov 2009 02:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-162878</guid>
		<description>Unless you&#039;re also going to force all plugins and themes to also be updated at exactly the same time as your forced Wordpress upgrade, what you&#039;re suggesting would result in a whole lot of people looking for a new platform.

If every time you upgrade Wordpress it breaks plugins that may be an important part of the site, because it doesn&#039;t want to do backward compatibility, how would that possibly be good for the end-user? It&#039;d just render the platform too unpredictable to use for any serious purpose.</description>
		<content:encoded><![CDATA[<p>Unless you&#8217;re also going to force all plugins and themes to also be updated at exactly the same time as your forced Wordpress upgrade, what you&#8217;re suggesting would result in a whole lot of people looking for a new platform.</p>
<p>If every time you upgrade Wordpress it breaks plugins that may be an important part of the site, because it doesn&#8217;t want to do backward compatibility, how would that possibly be good for the end-user? It&#8217;d just render the platform too unpredictable to use for any serious purpose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cracker</title>
		<link>http://justintadlock.com/archives/2009/09/22/plugin-and-theme-authors-should-force-users-to-upgrade#comment-162233</link>
		<dc:creator>cracker</dc:creator>
		<pubDate>Fri, 13 Nov 2009 04:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=1829#comment-162233</guid>
		<description>Wow Great point Justin!

i love wordpress  ^^</description>
		<content:encoded><![CDATA[<p>Wow Great point Justin!</p>
<p>i love wordpress  ^^</p>
]]></content:encoded>
	</item>
</channel>
</rss>
