<?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: Trouble With Future Posts</title>
	<atom:link href="http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/feed/" rel="self" type="application/rss+xml" />
	<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/</link>
	<description>Helping you learn more and do more with WordPress</description>
	<lastBuildDate>Tue, 21 May 2013 10:14:42 +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/04/11/wordpresscom-trouble-with-future-posts/#comment-907159</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Fri, 25 Jul 2008 01:43:48 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-907159</guid>
		<description><![CDATA[@&lt;a href=&quot;http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-907127&quot; rel=&quot;nofollow&quot;&gt; Mark&lt;/a&gt;:

Thanks for the information, however that wasn&#039;t the issue that caused this problem. It was a glitch in the WordPressMU core programming. Sorry that it is happening to you in this way. Are you sure this is the answer? I&#039;ve used http protection and never had future posts release early. Very odd. Might be your particular setup.]]></description>
		<content:encoded><![CDATA[<p>@<a href="http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-907127" rel="nofollow"> Mark</a>:</p>
<p>Thanks for the information, however that wasn&#8217;t the issue that caused this problem. It was a glitch in the WordPressMU core programming. Sorry that it is happening to you in this way. Are you sure this is the answer? I&#8217;ve used http protection and never had future posts release early. Very odd. Might be your particular setup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-907127</link>
		<dc:creator><![CDATA[Mark]]></dc:creator>
		<pubDate>Thu, 24 Jul 2008 09:52:13 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-907127</guid>
		<description><![CDATA[I experienced similar problems. Sure, it happens when you switch on HTTP protection. Maybe it&#039;s not everyone&#039;s case, but &lt;a href=&quot;http://blog.mvpnetwork.it/2008/07/24/wordpress-scheduled-post-not-working-heres-a-reason/&quot; rel=&quot;nofollow&quot;&gt;I&#039;ve explained it on my blog&lt;/a&gt;. Hope can be useful.
Mark]]></description>
		<content:encoded><![CDATA[<p>I experienced similar problems. Sure, it happens when you switch on HTTP protection. Maybe it&#8217;s not everyone&#8217;s case, but <a href="http://blog.mvpnetwork.it/2008/07/24/wordpress-scheduled-post-not-working-heres-a-reason/" rel="nofollow">I&#8217;ve explained it on my blog</a>. Hope can be useful.<br />
Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog Struggles: Surviving Offline Downtime &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-892816</link>
		<dc:creator><![CDATA[Blog Struggles: Surviving Offline Downtime &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Thu, 13 Mar 2008 00:35:34 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-892816</guid>
		<description><![CDATA[[...] all future posts were posting. The development team worked overtime and finally fixed it, then it broken again. A few days later, WordPress.com&#8217;s server crashed and I lost a few posts in the big bang. It [...]]]></description>
		<content:encoded><![CDATA[<p>[...] all future posts were posting. The development team worked overtime and finally fixed it, then it broken again. A few days later, WordPress.com&#8217;s server crashed and I lost a few posts in the big bang. It [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Interface and Administration Panels Coming for WordPress.com &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-861406</link>
		<dc:creator><![CDATA[New Interface and Administration Panels Coming for WordPress.com &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Fri, 04 Jan 2008 20:35:33 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-861406</guid>
		<description><![CDATA[[...] listed in the Dashboard (they disappeared a couple months ago from Wordpress.com - about the time future posts also stopped working) in chronological order distinctively from the most recent released [...]]]></description>
		<content:encoded><![CDATA[<p>[...] listed in the Dashboard (they disappeared a couple months ago from WordPress.com &#8211; about the time future posts also stopped working) in chronological order distinctively from the most recent released [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Bug Hunt</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-18107</link>
		<dc:creator><![CDATA[WordPress Bug Hunt]]></dc:creator>
		<pubDate>Fri, 30 Jun 2006 06:30:45 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-18107</guid>
		<description><![CDATA[[...] Lorelle has reported a few Wordpress.com Bugs - Anonymous Trackbacks and Comments, Trouble with Future Posts [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Lorelle has reported a few WordPress.com Bugs &#8211; Anonymous Trackbacks and Comments, Trouble with Future Posts [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle on WordPress &#187; What Are Your Favorite Articles from Lorelle on WordPress?</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-15226</link>
		<dc:creator><![CDATA[Lorelle on WordPress &#187; What Are Your Favorite Articles from Lorelle on WordPress?]]></dc:creator>
		<pubDate>Fri, 16 Jun 2006 14:53:20 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-15226</guid>
		<description><![CDATA[[...] I will be on the road again - actually I&#8217;m still on the road and have been constantly since March, but will be out of Internet range for most of the next week. Future posts are still not working, so while there are wonderful things you should be reading here, I don&#8217;t trust them to self-publish. Sorry. Without me to click the buttons, future posts won&#8217;t release. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] I will be on the road again &#8211; actually I&#8217;m still on the road and have been constantly since March, but will be out of Internet range for most of the next week. Future posts are still not working, so while there are wonderful things you should be reading here, I don&#8217;t trust them to self-publish. Sorry. Without me to click the buttons, future posts won&#8217;t release. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-7068</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Tue, 18 Apr 2006 14:02:21 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-7068</guid>
		<description><![CDATA[Thanks for the tip, Mark, and I&#039;ll be digging into the hype soon to help everyone understand the differences and the change.

As for now, I&#039;m on the road still and going bonkers with the lack of future posts releasing. Finding an Internet connection every day instead of every other or three days in order to feed the fans adds to the stress of this trip. And trust me, this has been an incredibly stressful trip. :-/

I hope this is fixed SOON!]]></description>
		<content:encoded><![CDATA[<p>Thanks for the tip, Mark, and I&#8217;ll be digging into the hype soon to help everyone understand the differences and the change.</p>
<p>As for now, I&#8217;m on the road still and going bonkers with the lack of future posts releasing. Finding an Internet connection every day instead of every other or three days in order to feed the fans adds to the stress of this trip. And trust me, this has been an incredibly stressful trip. :-/</p>
<p>I hope this is fixed SOON!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Jaquith</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-7051</link>
		<dc:creator><![CDATA[Mark Jaquith]]></dc:creator>
		<pubDate>Tue, 18 Apr 2006 08:07:16 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-7051</guid>
		<description><![CDATA[WordPress 2.1 (Which WordPress MU/wordpress.com share much of their code with) addresses future posts in a different way than WordPress 2.0.2 (and all previous versions, for that matter).  I don&#039;t know if the problems you&#039;ve been having here are related that change solely, or if some aspect of the specific setup here at wordpress.com is compounding the matter, but hopefully it is being looked at, if you submitted feedback about the issue!

The good news is that the change in the way future posts are handled makes WordPress faster, especially for that all-important front page display.  It also opens the door for plugin authors to use the new pseudo-cron system to schedule events to happen at some future time, without having to all write their own implementation of that functionality. &lt;/hype&gt;]]></description>
		<content:encoded><![CDATA[<p>WordPress 2.1 (Which WordPress MU/wordpress.com share much of their code with) addresses future posts in a different way than WordPress 2.0.2 (and all previous versions, for that matter).  I don&#8217;t know if the problems you&#8217;ve been having here are related that change solely, or if some aspect of the specific setup here at wordpress.com is compounding the matter, but hopefully it is being looked at, if you submitted feedback about the issue!</p>
<p>The good news is that the change in the way future posts are handled makes WordPress faster, especially for that all-important front page display.  It also opens the door for plugin authors to use the new pseudo-cron system to schedule events to happen at some future time, without having to all write their own implementation of that functionality. &lt;/hype&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: girlfriday</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-6802</link>
		<dc:creator><![CDATA[girlfriday]]></dc:creator>
		<pubDate>Fri, 14 Apr 2006 03:18:10 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-6802</guid>
		<description><![CDATA[Thanks for this post.  I thought it was &#039;just me&#039; ... I&#039;ve sent a feedback to the developers (even though I&#039;m not sure how that works either).  Hope they fix it, because future posts that need to be manually triggered to publish aren&#039;t that useful as future posts ...]]></description>
		<content:encoded><![CDATA[<p>Thanks for this post.  I thought it was &#8216;just me&#8217; &#8230; I&#8217;ve sent a feedback to the developers (even though I&#8217;m not sure how that works either).  Hope they fix it, because future posts that need to be manually triggered to publish aren&#8217;t that useful as future posts &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blagermeister</title>
		<link>http://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-6669</link>
		<dc:creator><![CDATA[blagermeister]]></dc:creator>
		<pubDate>Thu, 13 Apr 2006 00:37:52 +0000</pubDate>
		<guid isPermaLink="false">https://lorelle.wordpress.com/2006/04/11/wordpresscom-trouble-with-future-posts/#comment-6669</guid>
		<description><![CDATA[I noticed the future post failure on a different blog when the time changed from daylight savings to standard time. Scheduled posts hung indefinitely. Very strange.]]></description>
		<content:encoded><![CDATA[<p>I noticed the future post failure on a different blog when the time changed from daylight savings to standard time. Scheduled posts hung indefinitely. Very strange.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
