<?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: 2.6.2 is FINE. Seriously.</title> <atom:link href="http://davemoyer.org/2008/09/15/262-is-fine-seriously/feed/" rel="self" type="application/rss+xml" /><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/</link> <description>Media Personality, Founder and President of Bitwire Media, Podcaster, Blogger, Audio and Video Producer</description> <lastBuildDate>Mon, 30 Aug 2010 16:11:30 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <item><title>By: Snoskred</title><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/comment-page-1/#comment-909</link> <dc:creator>Snoskred</dc:creator> <pubDate>Tue, 16 Sep 2008 17:00:12 +0000</pubDate> <guid isPermaLink="false">http://davemoyer.org/?p=128#comment-909</guid> <description>It might be fine for you, but it isn&#039;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice - if it turns out not be fine for them they won&#039;t be exactly thrilled.I&#039;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function - if you can&#039;t do that, you can&#039;t write a post or moderate comments or do anything!I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.And the most vital piece of advice you as a blogger should give to fellow bloggers is - if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#039;t suggest they should back up? Disaster for the blogger.. :(And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#039;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#039;t know why Wordpress is choosing to go down the path they are, but it is upsetting plenty of people.</description> <content:encoded><![CDATA[<p>It might be fine for you, but it isn&#8217;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice &#8211; if it turns out not be fine for them they won&#8217;t be exactly thrilled.</p><p>I&#8217;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.</p><p>People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function &#8211; if you can&#8217;t do that, you can&#8217;t write a post or moderate comments or do anything!</p><p>I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.</p><p>And the most vital piece of advice you as a blogger should give to fellow bloggers is &#8211; if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#8217;t suggest they should back up? Disaster for the blogger.. :(</p><p>And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#8217;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#8217;t know why WordPress is choosing to go down the path they are, but it is upsetting plenty of people.</p> ]]></content:encoded> </item> <item><title>By: Sephyroth</title> <atom:link href="http://davemoyer.org/2008/09/15/262-is-fine-seriously/feed/" rel="self" type="application/rss+xml" /><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/</link> <description>Media Personality, Founder and President of Bitwire Media, Podcaster, Blogger, Audio and Video Producer</description> <lastBuildDate>Mon, 30 Aug 2010 16:11:30 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <item><title>Comments on: 2.6.2 is FINE. Seriously.</title> <atom:link href="http://davemoyer.org/2008/09/15/262-is-fine-seriously/feed/" rel="self" type="application/rss+xml" /><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/</link> <description>Media Personality, Founder and President of Bitwire Media, Podcaster, Blogger, Audio and Video Producer</description> <lastBuildDate>Mon, 30 Aug 2010 16:11:30 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <item><title>By: Snoskred</title><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/comment-page-1/#comment-909</link> <dc:creator>Snoskred</dc:creator> <pubDate>Tue, 16 Sep 2008 17:00:12 +0000</pubDate> <guid isPermaLink="false">http://davemoyer.org/?p=128#comment-909</guid> <description>It might be fine for you, but it isn&#039;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice - if it turns out not be fine for them they won&#039;t be exactly thrilled.I&#039;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function - if you can&#039;t do that, you can&#039;t write a post or moderate comments or do anything!I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.And the most vital piece of advice you as a blogger should give to fellow bloggers is - if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#039;t suggest they should back up? Disaster for the blogger.. :(And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#039;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#039;t know why Wordpress is choosing to go down the path they are, but it is upsetting plenty of people.</description> <content:encoded><![CDATA[<p>It might be fine for you, but it isn&#8217;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice &#8211; if it turns out not be fine for them they won&#8217;t be exactly thrilled.</p><p>I&#8217;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.</p><p>People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function &#8211; if you can&#8217;t do that, you can&#8217;t write a post or moderate comments or do anything!</p><p>I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.</p><p>And the most vital piece of advice you as a blogger should give to fellow bloggers is &#8211; if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#8217;t suggest they should back up? Disaster for the blogger.. :(</p><p>And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#8217;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#8217;t know why WordPress is choosing to go down the path they are, but it is upsetting plenty of people.</p> ]]></content:encoded> </item> <item><title>By: Sephyroth</title><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/comment-page-1/#comment-909</link> <dc:creator>Snoskred</dc:creator> <pubDate>Tue, 16 Sep 2008 17:00:12 +0000</pubDate> <guid isPermaLink="false">http://davemoyer.org/?p=128#comment-909</guid> <description>It might be fine for you, but it isn&#039;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice - if it turns out not be fine for them they won&#039;t be exactly thrilled.I&#039;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function - if you can&#039;t do that, you can&#039;t write a post or moderate comments or do anything!I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.And the most vital piece of advice you as a blogger should give to fellow bloggers is - if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#039;t suggest they should back up? Disaster for the blogger.. :(And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#039;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#039;t know why Wordpress is choosing to go down the path they are, but it is upsetting plenty of people.</description> <content:encoded><![CDATA[<p>It might be fine for you, but it isn&#8217;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice &#8211; if it turns out not be fine for them they won&#8217;t be exactly thrilled.</p><p>I&#8217;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.</p><p>People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function &#8211; if you can&#8217;t do that, you can&#8217;t write a post or moderate comments or do anything!</p><p>I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.</p><p>And the most vital piece of advice you as a blogger should give to fellow bloggers is &#8211; if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#8217;t suggest they should back up? Disaster for the blogger.. :(</p><p>And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#8217;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#8217;t know why WordPress is choosing to go down the path they are, but it is upsetting plenty of people.</p> ]]></content:encoded> </item> <item><title>Comments on: 2.6.2 is FINE. Seriously.</title> <atom:link href="http://davemoyer.org/2008/09/15/262-is-fine-seriously/feed/" rel="self" type="application/rss+xml" /><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/</link> <description>Media Personality, Founder and President of Bitwire Media, Podcaster, Blogger, Audio and Video Producer</description> <lastBuildDate>Mon, 30 Aug 2010 16:11:30 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <item><title>By: Snoskred</title><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/comment-page-1/#comment-909</link> <dc:creator>Snoskred</dc:creator> <pubDate>Tue, 16 Sep 2008 17:00:12 +0000</pubDate> <guid isPermaLink="false">http://davemoyer.org/?p=128#comment-909</guid> <description>It might be fine for you, but it isn&#039;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice - if it turns out not be fine for them they won&#039;t be exactly thrilled.I&#039;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function - if you can&#039;t do that, you can&#039;t write a post or moderate comments or do anything!I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.And the most vital piece of advice you as a blogger should give to fellow bloggers is - if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#039;t suggest they should back up? Disaster for the blogger.. :(And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#039;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#039;t know why Wordpress is choosing to go down the path they are, but it is upsetting plenty of people.</description> <content:encoded><![CDATA[<p>It might be fine for you, but it isn&#8217;t fine for an awful lot of people. So let me sound the note of caution that telling people to upgrade because it was fine for you is potentially a dangerous piece of advice to be giving out to fellow bloggers who might be relying on your advice &#8211; if it turns out not be fine for them they won&#8217;t be exactly thrilled.</p><p>I&#8217;m not saying it based purely on my own experience, I based it on the experience other people had as well, and also after reading the support forums long enough to get a king size migraine. Because that place is not somewhere fun to hang out, unfortunately.</p><p>People are still having issues with the problems I mentioned right now today. And logging in to your blog is quite a vital function &#8211; if you can&#8217;t do that, you can&#8217;t write a post or moderate comments or do anything!</p><p>I believe better advice to give to people reading your blog is to be cautious, check things out before you upgrade, read the support forums to see what problems they are having and perhaps wait for a later, less buggy version.</p><p>And the most vital piece of advice you as a blogger should give to fellow bloggers is &#8211; if people do want to upgrade, backup and be prepared to use the backup if you need to. Because if things happen to go wrong and you were the reason they upgraded because it was fine for you, and you didn&#8217;t suggest they should back up? Disaster for the blogger.. :(</p><p>And in my case, I gave the advice I did because I feel very strongly about it. I still stand by it. 2.3.3 is perfectly safe as long as you disallow user registration. It doesn&#8217;t have a lot of the issues that happened with later versions. Bloggers want to be able to blog, not to have to deal with bugs. I don&#8217;t know why WordPress is choosing to go down the path they are, but it is upsetting plenty of people.</p> ]]></content:encoded> </item> <item><title>By: Sephyroth</title><link>http://davemoyer.org/2008/09/15/262-is-fine-seriously/comment-page-1/#comment-908</link> <dc:creator>Sephyroth</dc:creator> <pubDate>Tue, 16 Sep 2008 16:52:53 +0000</pubDate> <guid isPermaLink="false">http://davemoyer.org/?p=128#comment-908</guid> <description>The issue described in the post is one where, on some sites, when you upgrade, you cannot access your blog&#039;s admin panel. I know that because it happened to me, and the suggested fix (clearing cookies) did not work, since I tried it in three separate browsers, with the same result.It is not something that I would call &quot;irrelevant and unimportant.&quot; That is, unless you don&#039;t consider being able to post to your site important.</description> <content:encoded><![CDATA[<p>The issue described in the post is one where, on some sites, when you upgrade, you cannot access your blog&#8217;s admin panel. I know that because it happened to me, and the suggested fix (clearing cookies) did not work, since I tried it in three separate browsers, with the same result.</p><p>It is not something that I would call &#8220;irrelevant and unimportant.&#8221; That is, unless you don&#8217;t consider being able to post to your site important.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)

Served from: davemoyer.org @ 2010-09-09 17:13:22 -->