<?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/"
	xmlns:georss="http://www.georss.org/georss" 	>
<channel>
	<title>Comments on: WordPress 2.2 upgrade caveats</title>
	<atom:link href="http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/feed/" rel="self" type="application/rss+xml" />
	<link>http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/</link>
	<description>K.G. Schneider's blog on librarianship, writing, and everything else</description>
	<lastBuildDate>Sun, 20 May 2012 03:37:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: david lee king</title>
		<link>http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/comment-page-1/#comment-5107</link>
		<dc:creator>david lee king</dc:creator>
		<pubDate>Mon, 21 May 2007 14:15:36 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/#comment-5107</guid>
		<description>Wow - you made it into David Weinberger&#039;s blog. Way to go!</description>
		<content:encoded><![CDATA[<p>Wow &#8211; you made it into David Weinberger&#8217;s blog. Way to go!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kgs</title>
		<link>http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/comment-page-1/#comment-5022</link>
		<dc:creator>kgs</dc:creator>
		<pubDate>Sun, 20 May 2007 16:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/#comment-5022</guid>
		<description>Here&#039;s my guess: the uber-gurus don&#039;t need written directions, and the one-click-install people ignore directions. So that leaves the QA for directions to savvy, smart people such as yourself, left wading through instructions that seem written in lolcatlish.

It&#039;s this bit-of-slipshoddiness that can make OS an unexpectedly hard sell. The last mile is crucial... and you *know* it will work and you *know* it&#039;s a good product, but it lacks the hospitality and transparent trustworthiness a product needs... that iPod-ish &quot;I luv this thing!&quot; experience. There are library parallels here, of course :-)</description>
		<content:encoded><![CDATA[<p>Here&#8217;s my guess: the uber-gurus don&#8217;t need written directions, and the one-click-install people ignore directions. So that leaves the QA for directions to savvy, smart people such as yourself, left wading through instructions that seem written in lolcatlish.</p>
<p>It&#8217;s this bit-of-slipshoddiness that can make OS an unexpectedly hard sell. The last mile is crucial&#8230; and you *know* it will work and you *know* it&#8217;s a good product, but it lacks the hospitality and transparent trustworthiness a product needs&#8230; that iPod-ish &#8220;I luv this thing!&#8221; experience. There are library parallels here, of course <img src='http://freerangelibrarian.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jessamyn</title>
		<link>http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/comment-page-1/#comment-5016</link>
		<dc:creator>jessamyn</dc:creator>
		<pubDate>Sun, 20 May 2007 13:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/#comment-5016</guid>
		<description>It&#039;s amazing to me that a blogging tool that is in use by as many people as WordPress can get away with still doing this kludgey form of upgrading. I&#039;m working on it today and the directions don&#039;t even really make sense. &quot;upload it to the WordPress directory, overwriting all the files that exist there only after you have delete the old files, which is explained as follows (do not overwrite your wp-content directory or wp-config.php).&quot; What? I&#039;d have more faith in the tool -- which I otherwise love -- if they would at least proofread their upgrade directions. For every sinlge person who comes through this thinking &quot;computers are hard, blogging is hard&quot;, I shake my fist at WordPress. It doesn&#039;t need to be like this.</description>
		<content:encoded><![CDATA[<p>It&#8217;s amazing to me that a blogging tool that is in use by as many people as WordPress can get away with still doing this kludgey form of upgrading. I&#8217;m working on it today and the directions don&#8217;t even really make sense. &#8220;upload it to the WordPress directory, overwriting all the files that exist there only after you have delete the old files, which is explained as follows (do not overwrite your wp-content directory or wp-config.php).&#8221; What? I&#8217;d have more faith in the tool &#8212; which I otherwise love &#8212; if they would at least proofread their upgrade directions. For every sinlge person who comes through this thinking &#8220;computers are hard, blogging is hard&#8221;, I shake my fist at WordPress. It doesn&#8217;t need to be like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sit tight and wait before upgrading to WP 2.2 &#187; wordpressgarage.com</title>
		<link>http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/comment-page-1/#comment-4994</link>
		<dc:creator>Sit tight and wait before upgrading to WP 2.2 &#187; wordpressgarage.com</dc:creator>
		<pubDate>Sun, 20 May 2007 06:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/#comment-4994</guid>
		<description>[...] WordPress 2.2 upgrade caveats - this guy&#8217;s upgrade didn&#8217;t go over so smoothly, and he had to spend several hours fixing things up. This post has a good list of things you should make sure to do before upgrading, including &#8220;having a backup theme or two hip-pocketed.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress 2.2 upgrade caveats - this guy&#8217;s upgrade didn&#8217;t go over so smoothly, and he had to spend several hours fixing things up. This post has a good list of things you should make sure to do before upgrading, including &#8220;having a backup theme or two hip-pocketed.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kgs</title>
		<link>http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/comment-page-1/#comment-4949</link>
		<dc:creator>kgs</dc:creator>
		<pubDate>Sat, 19 May 2007 20:55:39 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/#comment-4949</guid>
		<description>Yeah, in theory I should love one-click installs, but they make me uneasy. If I could handle Movable Type upgrades for close to four years, WP can&#039;t be that daunting.</description>
		<content:encoded><![CDATA[<p>Yeah, in theory I should love one-click installs, but they make me uneasy. If I could handle Movable Type upgrades for close to four years, WP can&#8217;t be that daunting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eas</title>
		<link>http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/comment-page-1/#comment-4940</link>
		<dc:creator>eas</dc:creator>
		<pubDate>Sat, 19 May 2007 19:07:47 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/05/19/wordpress-22-upgrade-caveats/#comment-4940</guid>
		<description>The inclusion of widgets into the Wordpress core also causes a problem with the beta releases of the popular and powerful K2 theme, which integrates a different, more flexible, widget handling system.

The solution for now involves a small plugin that disables wordpress 2.2&#039;s built in widgets:  http://getk2.com/forum/showthread.php?t=4143

Other than that, my upgrade went smoothly, helped by the fact that I didn&#039;t use a one-step upgrade.</description>
		<content:encoded><![CDATA[<p>The inclusion of widgets into the WordPress core also causes a problem with the beta releases of the popular and powerful K2 theme, which integrates a different, more flexible, widget handling system.</p>
<p>The solution for now involves a small plugin that disables wordpress 2.2&#8242;s built in widgets:  <a href="http://getk2.com/forum/showthread.php?t=4143" rel="nofollow">http://getk2.com/forum/showthread.php?t=4143</a></p>
<p>Other than that, my upgrade went smoothly, helped by the fact that I didn&#8217;t use a one-step upgrade.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.283 seconds -->

