<?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.com Future Post Bug: New Twist</title>
	<atom:link href="http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/feed/" rel="self" type="application/rss+xml" />
	<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/</link>
	<description>Helping you learn more and do more with WordPress</description>
	<lastBuildDate>Wed, 22 May 2013 03:04:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-906167</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Thu, 03 Jul 2008 15:23:25 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-906167</guid>
		<description><![CDATA[@&lt;a href=&quot;http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-906138&quot; rel=&quot;nofollow&quot;&gt; Josho&lt;/a&gt;:

This was a &quot;bug&quot; that happened in 2006 - actually in the first year of WordPress.com on and off. There was no design decisions or purposeful decisions to cause this bug. In the latest version of WordPress, the timestamp feature has been completely changed and now you do get to &quot;publish now&quot; with your blog posts. :D]]></description>
		<content:encoded><![CDATA[<p>@<a href="http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-906138" rel="nofollow"> Josho</a>:</p>
<p>This was a &#8220;bug&#8221; that happened in 2006 &#8211; actually in the first year of WordPress.com on and off. There was no design decisions or purposeful decisions to cause this bug. In the latest version of WordPress, the timestamp feature has been completely changed and now you do get to &#8220;publish now&#8221; with your blog posts. <img src='http://s0.wp.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josho</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-906138</link>
		<dc:creator><![CDATA[Josho]]></dc:creator>
		<pubDate>Thu, 03 Jul 2008 11:34:42 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-906138</guid>
		<description><![CDATA[It seems like this is not so much a bug as a &quot;design decision&quot; (though not a feature). The &quot;Publish&quot; button should be labelled &quot;Publish Now&quot;. If you want to schedule a post, edit the timestamp and change the status to Published using the drop-down box, then hit &quot;Save&quot;, not &quot;Publish[ Now]&quot;.]]></description>
		<content:encoded><![CDATA[<p>It seems like this is not so much a bug as a &#8220;design decision&#8221; (though not a feature). The &#8220;Publish&#8221; button should be labelled &#8220;Publish Now&#8221;. If you want to schedule a post, edit the timestamp and change the status to Published using the drop-down box, then hit &#8220;Save&#8221;, not &#8220;Publish[ Now]&#8220;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Cómo programar futuras publicaciones automáticas en Wordpress 2.0.5 &#124; Maikelnai&#8217;s blog</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-196563</link>
		<dc:creator><![CDATA[&#187; Cómo programar futuras publicaciones automáticas en Wordpress 2.0.5 &#124; Maikelnai&#8217;s blog]]></dc:creator>
		<pubDate>Tue, 27 Mar 2007 16:29:36 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-196563</guid>
		<description><![CDATA[[...] Extraído de Lorelle on Wordpress [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Extraído de Lorelle on WordPress [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jamesthoenes</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24292</link>
		<dc:creator><![CDATA[jamesthoenes]]></dc:creator>
		<pubDate>Sat, 29 Jul 2006 18:14:33 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24292</guid>
		<description><![CDATA[It took me a while to figure out what was going on.
The title for When the Blog Breaks came through on my Bloglines.
Looking forward to Aug when it already will have been released today back then (future particle past perfect present progressive verb tense).
James]]></description>
		<content:encoded><![CDATA[<p>It took me a while to figure out what was going on.<br />
The title for When the Blog Breaks came through on my Bloglines.<br />
Looking forward to Aug when it already will have been released today back then (future particle past perfect present progressive verb tense).<br />
James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24038</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Fri, 28 Jul 2006 12:03:42 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24038</guid>
		<description><![CDATA[Yep, only a problem with Wordpress.com.

It seems that future posts are posting...FINALLY, but that there are still bugs in the process. They are working on it, but I&#039;m now really nervous about editing anything or adding any more future posts until this is fixed.

I found that by editing anything, future or otherwise, within a few minutes of the last save and check, a future post within the next three or four days will release. I&#039;ll grab it and &quot;put it back&quot; but it might release again. It&#039;s a watching game. 

Who cares about staying up through the blogathon. I&#039;m not sleeping watching the site to make sure nothing from the future releases! ;-)

Thanks everyone for your help and keep reporting in. It helps us to understand that 1) this is not just Lorelle&#039;s blog that&#039;s screwed up, and 2) what you are seeing and experiencing.]]></description>
		<content:encoded><![CDATA[<p>Yep, only a problem with WordPress.com.</p>
<p>It seems that future posts are posting&#8230;FINALLY, but that there are still bugs in the process. They are working on it, but I&#8217;m now really nervous about editing anything or adding any more future posts until this is fixed.</p>
<p>I found that by editing anything, future or otherwise, within a few minutes of the last save and check, a future post within the next three or four days will release. I&#8217;ll grab it and &#8220;put it back&#8221; but it might release again. It&#8217;s a watching game. </p>
<p>Who cares about staying up through the blogathon. I&#8217;m not sleeping watching the site to make sure nothing from the future releases! <img src='http://s1.wp.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Thanks everyone for your help and keep reporting in. It helps us to understand that 1) this is not just Lorelle&#8217;s blog that&#8217;s screwed up, and 2) what you are seeing and experiencing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Collin</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24003</link>
		<dc:creator><![CDATA[Collin]]></dc:creator>
		<pubDate>Fri, 28 Jul 2006 07:37:40 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24003</guid>
		<description><![CDATA[Lorelle - I have seen the one about what to do with wordpress.com and the &quot;which c are b&quot; scheduled for the 31st.

As you&#039;ve said previously, this only seems to be a problem for wp.com.

I have months worth of posts scheduled at my photo blog and have no problem with them releasing on time.

Collin]]></description>
		<content:encoded><![CDATA[<p>Lorelle &#8211; I have seen the one about what to do with wordpress.com and the &#8220;which c are b&#8221; scheduled for the 31st.</p>
<p>As you&#8217;ve said previously, this only seems to be a problem for wp.com.</p>
<p>I have months worth of posts scheduled at my photo blog and have no problem with them releasing on time.</p>
<p>Collin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimbo</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24001</link>
		<dc:creator><![CDATA[Jimbo]]></dc:creator>
		<pubDate>Fri, 28 Jul 2006 07:34:50 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-24001</guid>
		<description><![CDATA[I saw the one scheduled for Monday (same as Mandarin) and the one that you already mentioned for the 29th.

I&#039;m not at home at the moment (damned work gets in the way!) so can&#039;t check.]]></description>
		<content:encoded><![CDATA[<p>I saw the one scheduled for Monday (same as Mandarin) and the one that you already mentioned for the 29th.</p>
<p>I&#8217;m not at home at the moment (damned work gets in the way!) so can&#8217;t check.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mandarine</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-23987</link>
		<dc:creator><![CDATA[mandarine]]></dc:creator>
		<pubDate>Fri, 28 Jul 2006 05:27:23 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-23987</guid>
		<description><![CDATA[Nope - I do not see that one. I see the one about &#039;which c. are b.&#039; And no other posts.]]></description>
		<content:encoded><![CDATA[<p>Nope &#8211; I do not see that one. I see the one about &#8216;which c. are b.&#8217; And no other posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-23938</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Fri, 28 Jul 2006 00:54:02 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-23938</guid>
		<description><![CDATA[Mandarine and Collin: do you see any other future post titles in your feed reader or just the one about what to do with Wordpress.com?]]></description>
		<content:encoded><![CDATA[<p>Mandarine and Collin: do you see any other future post titles in your feed reader or just the one about what to do with WordPress.com?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mandarine</title>
		<link>http://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-23870</link>
		<dc:creator><![CDATA[mandarine]]></dc:creator>
		<pubDate>Thu, 27 Jul 2006 21:16:11 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/07/27/wordpresscom-future-post-bug-new-twist/#comment-23870</guid>
		<description><![CDATA[I am using Akregator (konqueror-based, I would guess), and I can see a post of next monday, with the title and a four-line excerpt, none of which seem to be disappearing.
But it&#039;s quite nice as a teaser. I know I have to wait until monday to read the rest.]]></description>
		<content:encoded><![CDATA[<p>I am using Akregator (konqueror-based, I would guess), and I can see a post of next monday, with the title and a four-line excerpt, none of which seem to be disappearing.<br />
But it&#8217;s quite nice as a teaser. I know I have to wait until monday to read the rest.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
