choco-cookie

Otto42, why yes I do have a test post scheduled for that time! I’m glad someone can read that ??

I also have one scheduled to post at a date/time of May 28, 2007 @ 22:34, which unfortunately was last night.

Dashboard seems to be holding the scheduled entries hostage!! (really need to whip it into shape, moosh! moosh!)

Personally, I’m getting a bit stumped by this. If it was just me then I would say I goofed up big time (ok, I probably did, but where oh where…), but here we have Animator struggling along with the same issue. Too bad we couldn’t figure out the commonality between us, and then find a nice work-around…

OK, since we’re here… yeap, I have phpmyadmin (my host loves me I guess)

Option ID 164,
option value a:2:{i:1180476345;a:1:{s:19:”publish_future_post”;a:1:{s:32:”7e4251348df5ebeea43a212b0d548ef8″;a:2:{s:8:”schedule”;b:0;s:4:”args”;a:1:{i:0;i:2734;}}}}s:7:”version”;i:2;}

Funny enough, the “doing cron” has an option value of 0.

(I’m using an actual cron job to use postie, but that’s not the point here…)

If wp-cron.php changed in version 2.1, and I don’t need trackback, pingbacks, or anything other then posting, is just reverting to a prior version of this one file a potential fix? Or has the way WP uses wp-cron.php fundamentally changed to the point only a new version works (or doesn’t work, whatever the case may be)?

And if I’m not getting any errors when hitting wp-cron.php, how does one trouble shoot that it’s not working correctly? There isn’t any feedback to go off of, like “yeah, you did it!” or “boo! error 5 million & 72, failure”? I checked my host server error logs and hit had nothing to go on either. Bummer.

Otto42: I can hit that page in my WP install and get a nice blank page, no apparent errors. I have other cron processes running on my blog (postie for moblogging) without a hitch.

This future posting problem worked prior to one of the last few WP updates. I’ve been with WP since version 1.x, and future posting my little heart out without a hitch until I’d guess 2.1 something-or-other came out.

I’m going to guess (right or wrong) that there was a change deep down in the WP code that killed this feature.

It’s almost as if WP can’t move ‘published’ (since the entry is in the database, it is considered published) entries from “future” and hidden from view, to “live” for the world to see.

If it was just a matter of hitting wp-cron.php, heck, I could live with that, but, sorry, it’s more then that.

This is a problem that I too am having. I don’t think it’s a “linux fedora 5” problem as I’m on an Apache setup and experiencing the exact same issue even after the upgrade to 2.2. Either no one really future posts, or no one is really screaming about this broken feature.

While I’m not sure if my problem was the same as yours, I also was shut off by my host when on of those pesky bots decided to scan every single blog entry I had ever made (2000+), and every picture ever posted (also 2000+). With the server load being detrimental, the host modified my htaccess file to shut me out. And while they thought that would fix things, the bot kept going.

It took me looking at the raw access logs and going into CPanel to deny the IPs generating all the activity. My host wasn’t going to do anything but keep shutting me off.

If you can see who is generating this extreme traffic on your site you may want to try a similar approach to cut it down.