<?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: WordPress v. 2.2 Upgrade Exposes Cracks in the Foundation</title>
	<atom:link href="http://www.mkbergman.com/382/wordpress-v-22-upgrade-exposes-cracks-in-the-foundation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mkbergman.com/382/wordpress-v-22-upgrade-exposes-cracks-in-the-foundation/</link>
	<description>Mike Bergman on the semantic Web and structured Web</description>
	<lastBuildDate>Wed, 01 Feb 2012 21:05:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Dave Wong</title>
		<link>http://www.mkbergman.com/382/wordpress-v-22-upgrade-exposes-cracks-in-the-foundation/comment-page-1/#comment-46069</link>
		<dc:creator>Dave Wong</dc:creator>
		<pubDate>Sat, 25 Aug 2007 15:20:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=382#comment-46069</guid>
		<description>There is bug in this advanced tinymce editor, the editor instead of stacking below the default tinymce editor, it just stack on the same line as the default one making so long that even protrude out the text box making it unsightly. It also make the Visual Code tag on top not responsive and make the loading of the page slower than usual.</description>
		<content:encoded><![CDATA[<p>There is bug in this advanced tinymce editor, the editor instead of stacking below the default tinymce editor, it just stack on the same line as the default one making so long that even protrude out the text box making it unsightly. It also make the Visual Code tag on top not responsive and make the loading of the page slower than usual.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ja</title>
		<link>http://www.mkbergman.com/382/wordpress-v-22-upgrade-exposes-cracks-in-the-foundation/comment-page-1/#comment-45494</link>
		<dc:creator>Ja</dc:creator>
		<pubDate>Tue, 03 Jul 2007 18:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=382#comment-45494</guid>
		<description>Wow, you really laid out the issues extremely well and because of the hassles involved as you noted people don&#039;t upgrade which leads to security problems.  Might be nice to at least have security-only updates separated from functionality updates.

I&#039;m not sure about Mozilla (Firefox) vs. Automattic (Wordpress) in terms of userbase, but Wordpress is the top dog in blogging these days and you&#039;d be surprised how many people use it.  The difference in quality of development, documentation, support, etc. comes down to an issue of money in my mind.  Mozilla makes a ton of money off of Firefox due to a deals like those it has with Google.  Basically, you have big money pushing the development and promotion of the browser which would drive up profits for all those monetarily involved.  There&#039;s I&#039;m guessing far less money behind Wordpress and the open-source development, while getting us free open-source software, at the end of the day benefits Automattic more than anyone else.  I&#039;m guessing if things were *too* good or *too* easy to maintain, Wordpress.com and their professional services might suffer a bit.  Then again, when I look at the web in general I really wonder why we do things the way we do when technology (and logic) offers such better alternatives but I guess it&#039;s more useful and realistic to try and improve what we have than to start a revolution.

One more thing... what caused you to suspect Post-Teaser wouldn&#039;t work with 2.2.x?  I still use the 2.0.x line personally but I tested it with 2.2 and found it didn&#039;t want to work when using the more tag in posts.  White screen as you mentioned.  I only tested it briefly but I&#039;m looking into the problem... I know where it occurs I&#039;m just not sure what&#039;s changed between 2.0.x and 2.2 so I&#039;ve got to go through changesets/diffs in trac and see what&#039;s changed.  I can see why plugin devs stop supporting their plugins... what a pain.

Great post...

Cheers,

JÃƒÆ’Ã†â€™Ãƒâ€ Ã¢â‚¬â„¢ÃƒÆ’Ã‚Â¢ÃƒÂ¢Ã¢â‚¬Å¡Ã‚Â¬Ãƒâ€¦Ã‚Â¾ Ãƒâ€šÃ‚Â</description>
		<content:encoded><![CDATA[<p>Wow, you really laid out the issues extremely well and because of the hassles involved as you noted people don&#8217;t upgrade which leads to security problems.  Might be nice to at least have security-only updates separated from functionality updates.</p>
<p>I&#8217;m not sure about Mozilla (Firefox) vs. Automattic (WordPress) in terms of userbase, but WordPress is the top dog in blogging these days and you&#8217;d be surprised how many people use it.  The difference in quality of development, documentation, support, etc. comes down to an issue of money in my mind.  Mozilla makes a ton of money off of Firefox due to a deals like those it has with Google.  Basically, you have big money pushing the development and promotion of the browser which would drive up profits for all those monetarily involved.  There&#8217;s I&#8217;m guessing far less money behind WordPress and the open-source development, while getting us free open-source software, at the end of the day benefits Automattic more than anyone else.  I&#8217;m guessing if things were *too* good or *too* easy to maintain, WordPress.com and their professional services might suffer a bit.  Then again, when I look at the web in general I really wonder why we do things the way we do when technology (and logic) offers such better alternatives but I guess it&#8217;s more useful and realistic to try and improve what we have than to start a revolution.</p>
<p>One more thing&#8230; what caused you to suspect Post-Teaser wouldn&#8217;t work with 2.2.x?  I still use the 2.0.x line personally but I tested it with 2.2 and found it didn&#8217;t want to work when using the more tag in posts.  White screen as you mentioned.  I only tested it briefly but I&#8217;m looking into the problem&#8230; I know where it occurs I&#8217;m just not sure what&#8217;s changed between 2.0.x and 2.2 so I&#8217;ve got to go through changesets/diffs in trac and see what&#8217;s changed.  I can see why plugin devs stop supporting their plugins&#8230; what a pain.</p>
<p>Great post&#8230;</p>
<p>Cheers,</p>
<p>JÃƒÆ’Ã†â€™Ãƒâ€ Ã¢â‚¬â„¢ÃƒÆ’Ã‚Â¢ÃƒÂ¢Ã¢â‚¬Å¡Ã‚Â¬Ãƒâ€¦Ã‚Â¾ Ãƒâ€šÃ‚Â</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angsuman Chakraborty</title>
		<link>http://www.mkbergman.com/382/wordpress-v-22-upgrade-exposes-cracks-in-the-foundation/comment-page-1/#comment-45321</link>
		<dc:creator>Angsuman Chakraborty</dc:creator>
		<pubDate>Thu, 14 Jun 2007 01:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=382#comment-45321</guid>
		<description>Thanks for the detailed posting. I have been thinking of upgrading my blogs to 2.2 for performance reasons; after this post I will wait.

&gt; ENABLE_CACHE. What it does and why or how is unclear, let alone other such possible settings.
It enables file based object cache which can improve performance. Unfortunately it also consumes more memory. I have seen it bring some sites to a crawl though personally it didn&#039;t create any problems.</description>
		<content:encoded><![CDATA[<p>Thanks for the detailed posting. I have been thinking of upgrading my blogs to 2.2 for performance reasons; after this post I will wait.</p>
<p>&gt; ENABLE_CACHE. What it does and why or how is unclear, let alone other such possible settings.<br />
It enables file based object cache which can improve performance. Unfortunately it also consumes more memory. I have seen it bring some sites to a crawl though personally it didn&#8217;t create any problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle</title>
		<link>http://www.mkbergman.com/382/wordpress-v-22-upgrade-exposes-cracks-in-the-foundation/comment-page-1/#comment-45278</link>
		<dc:creator>Lorelle</dc:creator>
		<pubDate>Sun, 10 Jun 2007 03:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=382#comment-45278</guid>
		<description>You are welcome and I did cover many tips on installation on the &lt;a href=&quot;http://www.blogherald.com/2007/05/30/wordpress-wednesday-news-1-million-wordpresscom-blogs-wordpress-22-upgrade-tips-news-on-wordpress-23-wordpress-plugin-competition-and-more/&quot; title=&quot;1 Million WordPress.com Blogs, WordPress 2.2 Upgrade Tips, News on WordPress 2.3, WordPress Plugin Competition, and More&quot; rel=&quot;nofollow&quot;&gt;Blog Herald&lt;/a&gt;. 

Also, Kaizenlog is a splog, so you might want to remove trackbacks from them.</description>
		<content:encoded><![CDATA[<p>You are welcome and I did cover many tips on installation on the <a href="http://www.blogherald.com/2007/05/30/wordpress-wednesday-news-1-million-wordpresscom-blogs-wordpress-22-upgrade-tips-news-on-wordpress-23-wordpress-plugin-competition-and-more/" title="1 Million WordPress.com Blogs, WordPress 2.2 Upgrade Tips, News on WordPress 2.3, WordPress Plugin Competition, and More" rel="nofollow">Blog Herald</a>. </p>
<p>Also, Kaizenlog is a splog, so you might want to remove trackbacks from them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

