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.
Postie uses a different type of cron, not the same thing at all. Unless you're using "cronless postie".
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.
2.1 added the new wp-cron.php functionality. What you suggest supports my argument, that your wp-cron is not working correctly.
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.
a) That's *not* what "published" means. Drafts are in the database too.
b) When the post_status field changes from "future" to "publish", *then* is is published. Not before. And wp-cron is what makes that happen, as of 2.1 and up. wp-cron does several other things too (pingbacks, trackbacks, etc).
If it was just a matter of hitting wp-cron.php, heck, I could live with that, but, sorry, it's more then that.
No, you're *not* supposed to hit wp-cron yourself. WordPress does that all by itself. However, if it cannot for various reasons, then you would see the same sort of symptoms you are both describing.
Running any weird plugins? Anything not explicitly listed as 2.1 compatible?
the feature of Scheduled publishing does not work.
If you're going to make silly blanket statements like this, then you can just solve your problem yourself. The fact is that future publishing *does* work, I do it all the time. It's not working *for you*, so please confine yourself to sane and rational discourse on this forum. Okay?