This is all strange because I have to schedule all of my posts here. Since I edited a post once it never lets me publish immediately. The only way I can get around an immediate post is to schedule it one minute from the time it actually is. Of course I only have this problem if I'm behind schedule and need to post immediately. I normally try to have it ready to post the day before it's due.

I haven't updated my WP yet but when I do it's nice to know I can fix the problem if I need to.

I love WP, but when it's acting up, I almost hate it. LOL

Thanks for the info Kevin.

Can you give me more details about this. I can try and look into this for you

Kevin

I believe this is because the timeout value is too short: wp_remote_post($cron_url, array(‘timeout’ => 0.01, ‘blocking’ => false));

When making a request to wp-cron.php, it won’t return until all cron jobs are executed. And 0.01 is too short. It doesn’t hurt to extend the time span, as much as 10 minutes even. It will return as long as the mature crons are fired up and executed; in most cases only a few seconds.

For those of you who know how to edit the /wp-includes/cron.php file, simply edit 0.01 to 10 and extend the time allowed for running future scheduled posts.

Detailed instructions for extending the timeout value in /wp-includes/cron.php are in this post.

But I'll have a closer look at Semiologic's bugfix just to satisfy my curiosity.

Thanks!