<?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: Upgrading Wordpress Made Easier?</title>
	<atom:link href="http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/feed" rel="self" type="application/rss+xml" />
	<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier</link>
	<description>making our stupidity help you</description>
	<lastBuildDate>Thu, 11 Mar 2010 14:45:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ray</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-9481</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Sun, 04 May 2008 09:43:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-9481</guid>
		<description>I agree - but don&#039;t you have to make your directories world writable first to use the plugins?</description>
		<content:encoded><![CDATA[<p>I agree &#8211; but don&#8217;t you have to make your directories world writable first to use the plugins?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL 5 Tutorials &#38; Articles</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-9480</link>
		<dc:creator>MySQL 5 Tutorials &#38; Articles</dc:creator>
		<pubDate>Sun, 04 May 2008 05:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-9480</guid>
		<description>Theres some plugins for wordpress 2.5 which is great that can do auto upgrades.  I&#039;d advise updating the sql first though not backing up your data can be severe.</description>
		<content:encoded><![CDATA[<p>Theres some plugins for wordpress 2.5 which is great that can do auto upgrades.  I&#8217;d advise updating the sql first though not backing up your data can be severe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hari</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6374</link>
		<dc:creator>hari</dc:creator>
		<pubDate>Sun, 06 May 2007 12:45:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6374</guid>
		<description>Oh and you want an example of a feature that cannot be turned off? smart quotes and autosave comes to mind readily. I&#039;ll think of some more later.</description>
		<content:encoded><![CDATA[<p>Oh and you want an example of a feature that cannot be turned off? smart quotes and autosave comes to mind readily. I&#8217;ll think of some more later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hari</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6373</link>
		<dc:creator>hari</dc:creator>
		<pubDate>Sun, 06 May 2007 12:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6373</guid>
		<description>Ryan, I know, that is the point but... let me give you an example of how developers&#039; attitudes differ.

Recently a couple of b2evolution developers posted comments on my blog about my review of b2evo. Their attitude was hardly like this. They were so open to suggestions and comments and were polite too. They appreciated the fact that I, a lowly nobody, gave their software a review and even clarified some of the points - and I was not even a b2evolution user. None of the WP devs seem to have this openness of mind when listening to their *own* users.

It&#039;s not about being FOSS or not. It&#039;s about developers attitude and I think the point here is that the WP developers seem too to be chasing popularity rather than merit. You&#039;re deciding on features based on how many people want them, not on what&#039;s good for WordPress... It&#039;s showing now... I don&#039;t think you even have a vision of where you want to see WP going - or if you do, you haven&#039;t communicated it to users properly.

So, we all know what you mean - it&#039;s FOSS and we can take your code and change it. To be frank, I don&#039;t have to even do that. I&#039;d find it easier if I can create my own blogging system from scratch... The point is about acknowledging existing users&#039; concerns about developing and accepting that there are areas where you&#039;ve fallen behind since 1.5.

If we could all easily convert from WP to another blogging system, we would do it and not keep complaining. There are numerous issues in converting content from one tool to another which makes it extremely difficult practically. So I am forced to continue using WordPress if only to preserve my past content.</description>
		<content:encoded><![CDATA[<p>Ryan, I know, that is the point but&#8230; let me give you an example of how developers&#8217; attitudes differ.</p>
<p>Recently a couple of b2evolution developers posted comments on my blog about my review of b2evo. Their attitude was hardly like this. They were so open to suggestions and comments and were polite too. They appreciated the fact that I, a lowly nobody, gave their software a review and even clarified some of the points &#8211; and I was not even a b2evolution user. None of the WP devs seem to have this openness of mind when listening to their *own* users.</p>
<p>It&#8217;s not about being FOSS or not. It&#8217;s about developers attitude and I think the point here is that the WP developers seem too to be chasing popularity rather than merit. You&#8217;re deciding on features based on how many people want them, not on what&#8217;s good for WordPress&#8230; It&#8217;s showing now&#8230; I don&#8217;t think you even have a vision of where you want to see WP going &#8211; or if you do, you haven&#8217;t communicated it to users properly.</p>
<p>So, we all know what you mean &#8211; it&#8217;s FOSS and we can take your code and change it. To be frank, I don&#8217;t have to even do that. I&#8217;d find it easier if I can create my own blogging system from scratch&#8230; The point is about acknowledging existing users&#8217; concerns about developing and accepting that there are areas where you&#8217;ve fallen behind since 1.5.</p>
<p>If we could all easily convert from WP to another blogging system, we would do it and not keep complaining. There are numerous issues in converting content from one tool to another which makes it extremely difficult practically. So I am forced to continue using WordPress if only to preserve my past content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6232</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 02 May 2007 19:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6232</guid>
		<description>&lt;blockquote&gt;I donâ€™t think Ryan Filtzer made a â€œthrowaway commentâ€, because it directly response to Wankâ€™s assertion that 1.5 is good enough for her.&lt;/blockquote&gt;

Thanks for the clarification on that Lloyd. No one seemed to pick that up.

BTW, I not sure what features people find so interfering. The WYSIWYG turns off. Mark Jaquith offers &lt;a href=&quot;http://txfx.net/code/wordpress/clutter-free/&quot; rel=&quot;nofollow&quot;&gt;Clutter Free&lt;/a&gt; which turns off most elements on the post screen.

If you want more/less features in WP, contract a developer to make you exactly what you need. That&#039;s what I do, when I can&#039;t do it myself.

Echoing what I&#039;ve said before, WP gives everyone options. If you don&#039;t like the default WP, do something about it.</description>
		<content:encoded><![CDATA[<blockquote><p>I donâ€™t think Ryan Filtzer made a â€œthrowaway commentâ€, because it directly response to Wankâ€™s assertion that 1.5 is good enough for her.</p></blockquote>
<p>Thanks for the clarification on that Lloyd. No one seemed to pick that up.</p>
<p>BTW, I not sure what features people find so interfering. The WYSIWYG turns off. Mark Jaquith offers <a href="http://txfx.net/code/wordpress/clutter-free/" rel="nofollow">Clutter Free</a> which turns off most elements on the post screen.</p>
<p>If you want more/less features in WP, contract a developer to make you exactly what you need. That&#8217;s what I do, when I can&#8217;t do it myself.</p>
<p>Echoing what I&#8217;ve said before, WP gives everyone options. If you don&#8217;t like the default WP, do something about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6157</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Sun, 29 Apr 2007 13:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6157</guid>
		<description>Dom - as Hari said, Technorati isn&#039;t that accurate :)  It says that it&#039;s 4 days now.</description>
		<content:encoded><![CDATA[<p>Dom &#8211; as Hari said, Technorati isn&#8217;t that accurate <img src='http://www.lostaddress.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   It says that it&#8217;s 4 days now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hari</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6147</link>
		<dc:creator>hari</dc:creator>
		<pubDate>Sun, 29 Apr 2007 04:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6147</guid>
		<description>Technorati is not very clever or accurate anyway :P</description>
		<content:encoded><![CDATA[<p>Technorati is not very clever or accurate anyway <img src='http://www.lostaddress.org/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dominic</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6137</link>
		<dc:creator>Dominic</dc:creator>
		<pubDate>Sat, 28 Apr 2007 22:24:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6137</guid>
		<description>I know it&#039;s completely irrelevant, but I thought you might like to know that Technorati thinks it&#039;s been 55 days since you last posted to this blog..</description>
		<content:encoded><![CDATA[<p>I know it&#8217;s completely irrelevant, but I thought you might like to know that Technorati thinks it&#8217;s been 55 days since you last posted to this blog..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hari</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6070</link>
		<dc:creator>hari</dc:creator>
		<pubDate>Fri, 27 Apr 2007 01:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6070</guid>
		<description>Wow some pretty illustrious company out here.

Matt, the thing that really bothered me was that 2.0.x and 2.1 series have nothing really substantial above 1.5.x (as far as features related to &lt;i&gt;core blogging&lt;/i&gt; goes), but it has become quite huge and bulky.

I appreciated the optional WYSIWYG editor, but unfortunately its usefulness is limited because it doesn&#039;t produce 100% XHTML compliant output (TinyMCE&#039;s fault) and also the new autosave feature is so bugging me that I am even tempted to throw my old blog and start elsewhere with a new blogging tool.

I like WordPress&#039;s templating and theming system and is probably the best out there and its got the biggest active plugin and theme community, but sometimes I think that too much popularity has made WP go off in new directions which is not always appreciated by the old guard.</description>
		<content:encoded><![CDATA[<p>Wow some pretty illustrious company out here.</p>
<p>Matt, the thing that really bothered me was that 2.0.x and 2.1 series have nothing really substantial above 1.5.x (as far as features related to <i>core blogging</i> goes), but it has become quite huge and bulky.</p>
<p>I appreciated the optional WYSIWYG editor, but unfortunately its usefulness is limited because it doesn&#8217;t produce 100% XHTML compliant output (TinyMCE&#8217;s fault) and also the new autosave feature is so bugging me that I am even tempted to throw my old blog and start elsewhere with a new blogging tool.</p>
<p>I like WordPress&#8217;s templating and theming system and is probably the best out there and its got the biggest active plugin and theme community, but sometimes I think that too much popularity has made WP go off in new directions which is not always appreciated by the old guard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moeffju</title>
		<link>http://www.lostaddress.org/2007/04/25/upgrading-wordpress-made-easier/comment-page-1#comment-6067</link>
		<dc:creator>moeffju</dc:creator>
		<pubDate>Thu, 26 Apr 2007 22:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostaddress.org/index.php/2007/04/25/upgrading-wordpress-made-easier/#comment-6067</guid>
		<description>That sounds reasonable and doable at first, but I suppose you would quickly hit a dependency wall. That is, some &#039;security only fix&#039; would depend on other major core changes, which in turn depend on yet more core changes, etc. If you were to manually backport security fixes -- in effect forking WordPress 1.5 -- this proposal could very well work out.

But instead forking WordPress 1.5, I think it would make more sense to get involved with Habari and make it really simple to switch from WP 1.5 to Habari. You save on bloat, and you get to do something cool at the same time :D</description>
		<content:encoded><![CDATA[<p>That sounds reasonable and doable at first, but I suppose you would quickly hit a dependency wall. That is, some &#8217;security only fix&#8217; would depend on other major core changes, which in turn depend on yet more core changes, etc. If you were to manually backport security fixes &#8212; in effect forking WordPress 1.5 &#8212; this proposal could very well work out.</p>
<p>But instead forking WordPress 1.5, I think it would make more sense to get involved with Habari and make it really simple to switch from WP 1.5 to Habari. You save on bloat, and you get to do something cool at the same time <img src='http://www.lostaddress.org/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
