Skip navigation

Apologies: Future Posts Released Again

WordPress.com NewsAs I have/will/did write in the future post, Blog Struggles: Surviving Offline Downtime, which released a week ahead of schedule due to a repeat of a glitch on WordPress.com that hasn’t been seen for well over a year, I depend upon the future posts feature of WordPress for my blog to keep going while I’m off doing something else.

Timing is everything and I’m now on my first real vacation with my husband that is not work released in 14 years and several weeks of future posts have released.

Yep, I’m not vacationing. I’m now working. So much for vacation. I just wanted three days off. SIGH. Some day.

I’ve posted a note on the WordPress.com Support Forums about the issue and let the developers know of the problem. If you are experiencing the same thing, use your Feedback or the Forum post to let them know. I offer some tips on how to deal with it from your end in the Forum post.

So forgive me if you do not see any new posts over the new few weeks. They are there, so pretend they arrived on the day they were supposed to. Or dig into my tags or categories and see what you missed over the past two and a half years of more than 2000 articles on this blog.

I’m also not sure what will happen when WordPress.com fixes this. Will the posts jump back into the queue and off the web pages of my blog? I can’t take back the pings and trackbacks, nor the incoming links from bloggers who’ve already read these premature blog ejaculations – so if they do go back to pre-publish status, I apologize for the 404 Page Errors.

Remember, it’s fun like this that reminds us of why we keep blogging. Or at least, I think it’s supposed to be. I’ll work on that as I try to get back to my non-working vacation.

UPDATE: One of the things on the “you can’t win” scenarios is that this post, written and published on February 6, 2008, is not at the top of the post queue on my blog’s front page so you can see it easily. The front page and multi-post page views of a WordPress blog displays posts in chronological order. Thus, it is listed three weeks down the list of posts. SIGH. Hopefully, you will find it among all the posts.



Site Search Tags: , , , , , ,

Feed on Lorelle on WordPress Subscribe Feedburner iconVia Feedburner Subscribe by Email
Copyright Lorelle VanFossen, the author of Blogging Tips, What Bloggers Won't Tell You About Blogging.

8 Comments

  1. Posted February 6, 2008 at 2:03 pm | Permalink

    Well, just feel reassured that for those people who subscribe to your feed, this post still showed up after the earlier flood of accidentally released posts.

  2. Posted February 6, 2008 at 2:16 pm | Permalink

    WordPress seems to be having software glitches of all kinds lately. That and constant service maintenance.

    I hope you do enjoy your vacation despite the problems.

  3. Posted February 6, 2008 at 10:10 pm | Permalink

    I re-published my “early” posts with the correct dates still there and everything and they stopped showing up and went back to their place in the queue. Sigh. Confused my readers but good, that one.

  4. Posted February 7, 2008 at 2:46 pm | Permalink

    I can now get ahead on my blog challenges:)

  5. Posted February 7, 2008 at 9:49 pm | Permalink

    Last time you were out of town, the posts showed in my reader on the correct day but way down in my queue because they had the earlier date. Now they show up today with their dates intact, for the future

    (I can read the future in GreatNews Reader, Feb 20 is here already! Does this mean I can monetize your blog down at the carnival?)

  6. Posted February 7, 2008 at 10:15 pm | Permalink

    @ mpb:

    Oh, honey, if you can make money off my future post debacle, have at it. :D

  7. Posted February 12, 2008 at 3:16 pm | Permalink

    I’ve given up on future posts because of the other bug they have on wordpress.com: future posts don’t get added to those tag pages we can’t opt out of.

  8. Posted February 15, 2008 at 1:13 pm | Permalink

    Apologies Lorelle! A server needed to be rebooted and it had a bad battery. On reboot its time was somehow in the future, and that caused the issue. You were a big help in helping us work out the previous issues with future posting, and as you say “hasn’t been seen for well over a year”, so for you and everyone else it was very important we give you even more protection from this type of issue.

    Hailin has found and implemented #5801 safety measure for cron to publish future post and with Matt and Barry’s assistance an additional safeguards in place, where on future posting the server will check to see if it has the same time as another server, and only publish if both clocks are the same. If the clocks are not the same, then it will notify our sys admin team.

    engtech, the tag issue is a really annoying issue and I think is an intermittent one that we still haven’t been able to isolate.


One Trackback/Pingback

  1. […] Apologies: Future Posts Released Again give you a clue as to what my week was like. Several weeks of future posts released that were meant to cover some indepth concentrated writing times. Ah, the joys of blogging on a state-of-the-art blog platform. […]

Post a Comment

Follow

Get every new post delivered to your Inbox.

Join 21,185 other followers

%d bloggers like this: