<?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" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: WordPress 2.0</title>
	<atom:link href="http://lorelle.wordpress.com/2005/12/27/wordpress-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/</link>
	<description>Helping you learn more and do more with WordPress</description>
	<lastBuildDate>Tue, 21 May 2013 13:02:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Do-It-Yourself Search Engine Optimization Guide &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-33559</link>
		<dc:creator><![CDATA[Do-It-Yourself Search Engine Optimization Guide &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Mon, 04 Sep 2006 14:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-33559</guid>
		<description><![CDATA[[...] The new WordPress 2.0 and WordPress.com offers instant previews of your post within your WordPress Theme, giving you a chance to really see what it looks like before you publish. If you are using an older version of WordPress, you can get the same live preview by typing in your blog URL with the post number in a new tab or window such as http://example.com/index.php?p=456. The post number appears in the Write Post Panel address bar after you have hit Save and Continue Editing. Using this method in all versions of WordPress, you can actually test your post with any web validator if you find you have problems and can&#8217;t track down the culprit easily. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The new WordPress 2.0 and WordPress.com offers instant previews of your post within your WordPress Theme, giving you a chance to really see what it looks like before you publish. If you are using an older version of WordPress, you can get the same live preview by typing in your blog URL with the post number in a new tab or window such as <a href="http://example.com/index.php?p=456" rel="nofollow">http://example.com/index.php?p=456</a>. The post number appears in the Write Post Panel address bar after you have hit Save and Continue Editing. Using this method in all versions of WordPress, you can actually test your post with any web validator if you find you have problems and can&#8217;t track down the culprit easily. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle on WordPress &#187; Do You Update Posts or Post Updates?</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2989</link>
		<dc:creator><![CDATA[Lorelle on WordPress &#187; Do You Update Posts or Post Updates?]]></dc:creator>
		<pubDate>Wed, 01 Mar 2006 13:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2989</guid>
		<description><![CDATA[[...] The issue of updating posts is not limited to developers of software, programs, utilities, WordPress Themes, WordPress Plugin, or other services, products or tools. It&#8217;s been over a month since the release of WordPress 2.0, and yesterday I remembered to update &#8220;WordPress Versions: How Many and What&#8217;s the Difference, one of the popular posts on this blog. It still talked about WordPress 1.5.2. Yikes! So I updated it so people can find current information rather than old news. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The issue of updating posts is not limited to developers of software, programs, utilities, WordPress Themes, WordPress Plugin, or other services, products or tools. It&#8217;s been over a month since the release of WordPress 2.0, and yesterday I remembered to update &#8220;WordPress Versions: How Many and What&#8217;s the Difference, one of the popular posts on this blog. It still talked about WordPress 1.5.2. Yikes! So I updated it so people can find current information rather than old news. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle on WordPress &#187; Problems with WordPress 2.01 Feeds</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2557</link>
		<dc:creator><![CDATA[Lorelle on WordPress &#187; Problems with WordPress 2.01 Feeds]]></dc:creator>
		<pubDate>Sun, 19 Feb 2006 20:16:06 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2557</guid>
		<description><![CDATA[[...] If you are experiencing problems with feeds with your WordPress blog after installing the new WordPress 2.0.1, then Flyweb has a fix for what might ail you. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] If you are experiencing problems with feeds with your WordPress blog after installing the new WordPress 2.0.1, then Flyweb has a fix for what might ail you. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle on WordPress &#187; WordPress Versions - How Many and What&#8217;s the Diff?</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2384</link>
		<dc:creator><![CDATA[Lorelle on WordPress &#187; WordPress Versions - How Many and What&#8217;s the Diff?]]></dc:creator>
		<pubDate>Mon, 13 Feb 2006 16:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2384</guid>
		<description><![CDATA[[...] The full version of WordPress is available for download from the official WordPress Download site. The latest version is WordPress 2.0. It&#8217;s free and easy to install. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The full version of WordPress is available for download from the official WordPress Download site. The latest version is WordPress 2.0. It&#8217;s free and easy to install. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle on WordPress &#187; Release of WordPress 2.0.1</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2186</link>
		<dc:creator><![CDATA[Lorelle on WordPress &#187; Release of WordPress 2.0.1]]></dc:creator>
		<pubDate>Wed, 01 Feb 2006 22:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-2186</guid>
		<description><![CDATA[[...] For more information, see my post on WordPress 2.0 Release. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] For more information, see my post on WordPress 2.0 Release. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle on WordPress &#187; WordPress 2.0 Breaks Ecto - Here&#8217;s the Fix</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1237</link>
		<dc:creator><![CDATA[Lorelle on WordPress &#187; WordPress 2.0 Breaks Ecto - Here&#8217;s the Fix]]></dc:creator>
		<pubDate>Thu, 05 Jan 2006 21:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1237</guid>
		<description><![CDATA[[...] If you are currently using Ecto to post to your WordPress blog, and you upgrade to WordPress 2.0, according to the Ecto developers, it will break Ecto. But rest assured, the WordPress Development team sprung into action and a fix is available. I recommend not to upgrade to WordPress 2.0 yet as it breaks file upload via ecto and other blog clients. I posted a message to the wordpress-testers mailing list and am hoping they can fix the bug&#8230;It worked in a previous 2.0 beta version that I had used, and there were several changes in the xmlrpc.php file between the two versions and all related to the upload function. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] If you are currently using Ecto to post to your WordPress blog, and you upgrade to WordPress 2.0, according to the Ecto developers, it will break Ecto. But rest assured, the WordPress Development team sprung into action and a fix is available. I recommend not to upgrade to WordPress 2.0 yet as it breaks file upload via ecto and other blog clients. I posted a message to the wordpress-testers mailing list and am hoping they can fix the bug&#8230;It worked in a previous 2.0 beta version that I had used, and there were several changes in the xmlrpc.php file between the two versions and all related to the upload function. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1203</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Tue, 03 Jan 2006 16:59:49 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1203</guid>
		<description><![CDATA[Deanna,

It appears as if you have partially solved the problem yourself. You have tracked it down to Mudbomb&#039;s WYSIWYG WordPress Plugin. But it might not be that plugin but the way it interacts with other plugins that may attach themselves to the Write Post panel like a tagging, keywords, or spell check plugin. They could be clashing.

The first thing to do is contact the plugin author. Do not upgrade until this problem is solved. It&#039;s good that you know you have the latest previous stable version, so keep it that way until the problem is fixed.

The second thing is to go through your plugins and  turn them off one by one to see if they impact your draft content. Turn one off, go to the Manage or Write Post panel and click on a draft. If the content is there, you may have found the co-conspirator. If it isn&#039;t, then go back to the Plugins panel and turn the plugin back on and go to the next.

I personally can&#039;t stand WYSIWYG, though I have to admit that the new one with WordPress 2.0 is nicer, they still have a long way to go to really fix it to my personal standards and blogging style.

Third, post a note on the &lt;a href=&quot;http://www.wordpress.org/support&quot; rel=&quot;nofollow&quot;&gt;WordPress Support Forum&lt;/a&gt; about the problem. Search first to see if someone else has had the similar problem and come up with an answer, and then ask. They are awesome folks there, ready and willing to help. But start with the plugin author first.

Also, take time to do a full &lt;a href=&quot;http://lorelle.wordpress.com/2005/09/20/backing-up-wordpress/&quot; rel=&quot;nofollow&quot;&gt;Backup of your WordPress blog&lt;/a&gt; right now to make sure that your hunt for the problem doesn&#039;t make things worse and you have something close to right to fall back on.

I&#039;ve lost plenty of posts for different reasons, especially during the massive test driving of WordPress.com (and WordPress 1.6/2.0 driving it), hours and hours of work gone in an instant. My husband is now used to seeing me sob over my computer, bashing my head against the keyboard, but this is how things are tested thoroughly, and I&#039;ve learned to save save save and backup backup backup and roll with the losses.

Thus, you get a better WordPress product, helped by my tears. ;-)

Good luck and let me know how it turned out so we can all learn from this.]]></description>
		<content:encoded><![CDATA[<p>Deanna,</p>
<p>It appears as if you have partially solved the problem yourself. You have tracked it down to Mudbomb&#8217;s WYSIWYG WordPress Plugin. But it might not be that plugin but the way it interacts with other plugins that may attach themselves to the Write Post panel like a tagging, keywords, or spell check plugin. They could be clashing.</p>
<p>The first thing to do is contact the plugin author. Do not upgrade until this problem is solved. It&#8217;s good that you know you have the latest previous stable version, so keep it that way until the problem is fixed.</p>
<p>The second thing is to go through your plugins and  turn them off one by one to see if they impact your draft content. Turn one off, go to the Manage or Write Post panel and click on a draft. If the content is there, you may have found the co-conspirator. If it isn&#8217;t, then go back to the Plugins panel and turn the plugin back on and go to the next.</p>
<p>I personally can&#8217;t stand WYSIWYG, though I have to admit that the new one with WordPress 2.0 is nicer, they still have a long way to go to really fix it to my personal standards and blogging style.</p>
<p>Third, post a note on the <a href="http://www.wordpress.org/support" rel="nofollow">WordPress Support Forum</a> about the problem. Search first to see if someone else has had the similar problem and come up with an answer, and then ask. They are awesome folks there, ready and willing to help. But start with the plugin author first.</p>
<p>Also, take time to do a full <a href="http://lorelle.wordpress.com/2005/09/20/backing-up-wordpress/" rel="nofollow">Backup of your WordPress blog</a> right now to make sure that your hunt for the problem doesn&#8217;t make things worse and you have something close to right to fall back on.</p>
<p>I&#8217;ve lost plenty of posts for different reasons, especially during the massive test driving of WordPress.com (and WordPress 1.6/2.0 driving it), hours and hours of work gone in an instant. My husband is now used to seeing me sob over my computer, bashing my head against the keyboard, but this is how things are tested thoroughly, and I&#8217;ve learned to save save save and backup backup backup and roll with the losses.</p>
<p>Thus, you get a better WordPress product, helped by my tears. <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Good luck and let me know how it turned out so we can all learn from this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Playpen</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1202</link>
		<dc:creator><![CDATA[Playpen]]></dc:creator>
		<pubDate>Tue, 03 Jan 2006 16:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1202</guid>
		<description><![CDATA[&lt;strong&gt;WP 2.0 broken permalinks and 404 error&lt;/strong&gt;

Ironically, the recent post I wrote about upgrading painlessly to Wordpress 2.0. This resulted in my trackback to Lorelle&#8217;s tips on upgrading not working correctly (as the trackback link led to a 404 error), so thanks to her for letting me know. ...]]></description>
		<content:encoded><![CDATA[<p><strong>WP 2.0 broken permalinks and 404 error</strong></p>
<p>Ironically, the recent post I wrote about upgrading painlessly to WordPress 2.0. This resulted in my trackback to Lorelle&#8217;s tips on upgrading not working correctly (as the trackback link led to a 404 error), so thanks to her for letting me know. &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deanna</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1200</link>
		<dc:creator><![CDATA[deanna]]></dc:creator>
		<pubDate>Tue, 03 Jan 2006 14:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1200</guid>
		<description><![CDATA[Hi Lorelle,

Thanks for your tips. I&quot;m not a techie. My designer rolled wp into my music site, so I&#039;m in no hurry to attempt an update. Last night, after being a holiday slacker, I decided to write a bunch of drafts to put up later. This morning, the draft titles are still there, but all the content is missing. When I try to edit existing blog entries, the same thing happens. The titles are there, but the content is not. The only plugin I use is the WYSIWYG for composing posts (http://mudbomb.com/archives/2005/02/02/wysiwyg-plugin-for-wordpress/). When I deactivate this plugin, the content reappears on my published entries, but my draft content is STILL missing even when the plugin is off.

Can you advise me? Is the problem the plugin? If it is, would it be affect my blog like this even though I have not upgraded to wp 2. I&#039;m still using 1.5.2

Thanks for your help. Good luck with your writing endeavors.

Deanna]]></description>
		<content:encoded><![CDATA[<p>Hi Lorelle,</p>
<p>Thanks for your tips. I&#8221;m not a techie. My designer rolled wp into my music site, so I&#8217;m in no hurry to attempt an update. Last night, after being a holiday slacker, I decided to write a bunch of drafts to put up later. This morning, the draft titles are still there, but all the content is missing. When I try to edit existing blog entries, the same thing happens. The titles are there, but the content is not. The only plugin I use is the WYSIWYG for composing posts (<a href="http://mudbomb.com/archives/2005/02/02/wysiwyg-plugin-for-wordpress/" rel="nofollow">http://mudbomb.com/archives/2005/02/02/wysiwyg-plugin-for-wordpress/</a>). When I deactivate this plugin, the content reappears on my published entries, but my draft content is STILL missing even when the plugin is off.</p>
<p>Can you advise me? Is the problem the plugin? If it is, would it be affect my blog like this even though I have not upgraded to wp 2. I&#8217;m still using 1.5.2</p>
<p>Thanks for your help. Good luck with your writing endeavors.</p>
<p>Deanna</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Playpen</title>
		<link>http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1190</link>
		<dc:creator><![CDATA[Playpen]]></dc:creator>
		<pubDate>Mon, 02 Jan 2006 08:16:06 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/2005/12/27/wordpress-20/#comment-1190</guid>
		<description><![CDATA[&lt;strong&gt;Playpen upgraded to Wordpress 2.0&lt;/strong&gt;

Playpen has now been upgraded to Wordpress 2.0 largely without pain. In fact, without any pain at all, although I was particularly careful to back-up everything possible and check the back-up. Lorelle has an excellent collection of tips and links about...]]></description>
		<content:encoded><![CDATA[<p><strong>Playpen upgraded to WordPress 2.0</strong></p>
<p>Playpen has now been upgraded to WordPress 2.0 largely without pain. In fact, without any pain at all, although I was particularly careful to back-up everything possible and check the back-up. Lorelle has an excellent collection of tips and links about&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
