Skip navigation Trouble With Future Posts

A few days ago I reported problems I’m having with of future posts not releasing when they are scheduled to be released. After a few days offline traveling, I find that three days of posts did not release.

Apologizes to my fans, but more importantly, if you are having problems with future posts not releasing on schedule with your blogs, please report the problem to the developers through your Feedback button to help them track down the problem.

If you aren’t having trouble with future posts, then consider letting them know as well, so they can determine if the new Widgets or something else that might be causing a conflict.

I’m still on the road, so if you are missing a few posts over the next few days, I apologize. I will manually release them when I find an Internet connection. Right now, they are far and few in between. Such is life on the road. Hopefully this will be fixed soon.


Site Search Tags: , , , , , , ,
Copyright Lorelle VanFossen


  1. Webosphere
    Posted April 11, 2006 at 1:03 am | Permalink

    I4m facing the same problem 😦 since 2 months ! Any solution ?

  2. Dan
    Posted April 11, 2006 at 4:47 am | Permalink

    Glad to hear what the problem was. When there were no posts from you for several days, I thought you were probably traveling, but I also wondered if something was wrong–a new post from you each morning generally comes like clockwork, and I look forward to reading what you’ve got to say.

  3. Posted April 12, 2006 at 9:26 am | Permalink

    I recently (as in two days ago) upgraded from WP 2.0 to WP 2.0.2, and have made no changes (yet) to any of the core files. Yesterday, after reading about your ‘future posts’ article, I became concerned and immediately created three future test-posts, one set to post after a few minutes, another after a few hours, and a third the next day (today). All three posts were released on schedule. I will also report this finding to the WordPress development team. Hope it helps!

  4. Posted April 12, 2006 at 9:43 am | Permalink

    I should have mentioned that future posts are working on my full version of WordPress sites. The problem seems to be restricted to blogs, where we can’t dig into the code ourselves.

    Having suffered horribly upgrading to WordPress 2.0.2, I’m glad your upgrade went well. 😉

  5. blagermeister
    Posted April 12, 2006 at 6:37 pm | Permalink

    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.

  6. Posted April 13, 2006 at 9:18 pm | Permalink

    Thanks for this post. I thought it was ‘just me’ … I’ve sent a feedback to the developers (even though I’m not sure how that works either). Hope they fix it, because future posts that need to be manually triggered to publish aren’t that useful as future posts …

  7. Posted April 18, 2006 at 2:07 am | Permalink

    WordPress 2.1 (Which WordPress MU/ 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’t know if the problems you’ve been having here are related that change solely, or if some aspect of the specific setup here at 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. </hype>

  8. Posted April 18, 2006 at 8:02 am | Permalink

    Thanks for the tip, Mark, and I’ll be digging into the hype soon to help everyone understand the differences and the change.

    As for now, I’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!

  9. Posted July 24, 2008 at 2:52 am | Permalink

    I experienced similar problems. Sure, it happens when you switch on HTTP protection. Maybe it’s not everyone’s case, but I’ve explained it on my blog. Hope can be useful.

  10. Posted July 24, 2008 at 6:43 pm | Permalink

    @ Mark:

    Thanks for the information, however that wasn’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’ve used http protection and never had future posts release early. Very odd. Might be your particular setup.

6 Trackbacks/Pingbacks

  1. […] I will be on the road again – actually I’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’t trust them to self-publish. Sorry. Without me to click the buttons, future posts won’t release. […]

  2. […] Lorelle has reported a few Bugs – Anonymous Trackbacks and Comments, Trouble with Future Posts […]

  3. […] listed in the Dashboard (they disappeared a couple months ago from – about the time future posts also stopped working) in chronological order distinctively from the most recent released […]

  4. […] all future posts were posting. The development team worked overtime and finally fixed it, then it broken again. A few days later,’s server crashed and I lost a few posts in the big bang. It […]

  5. […] adding feeds to your WordPress Dashboard. It was in a post that didn’t release because of the damn future-posts-not-posting bug. Since it’s almost verbatim what Jim wrote, I won’t release it. I wonder how many posts […]

  6. […] my faulty Post Slug case, because future posts are still not working on blogs, I have to click Edit, then SAVE after the publish time and date in order for them to post. I did […]

Post a Comment

Required fields are marked *

%d bloggers like this: