Missed Schedule

Here goes a dump of my wp_options table

(removed by moderator – we really don’t need your options table.)

Posts scheduled before the upgrade seem to be missed, but all posts scheduled POST upgrade seem to be okay.

Actually posts scheduled after the upgrade still show as missed schedule!
This is what happened this morning: I’ve created a new post (not an imported post) and scheduled it for 8AM this morning, at 8:30 it showed up as missed schedule. I had to make this post private and then public to have it published on the blog.

Install the WP-Crontrol plugin. It will let you manually run those missed wp-cron jobs to force the publish to work. And you really do need to run them, even if you already published them manually. That will get rid of the cron jobs, at least.

Then you can start investigating why your wp-cron is not running properly. Usually this is a webserver configuration issue.

I’ve installed WP-Crontrol but it says that it’s compatible up to 2.5.1, not 2.7.
After install I got the following warning message:
Warning: array_merge() [function.array-merge]: Argument #1 is not an array in ..\wp-content\plugins\wp-crontrol\wp-crontrol.php on line 290

Anyway, I’ve installed WP-Crontrol, got rid of old events and uninstalled WP-Crontrol.

Now, how can I verify if this is a webserver config issue or not ?

Now, how can I verify if this is a webserver config issue or not ?

If you make a new post and some “do_pings” events show up in WP-Crontrol and never go away, then it’s a webserver config issue.

Getting the same issue here, I also got the same issues with 2.6 and above. I read somewhere not long ago that this issue with apparent cron server configuration issues would be fixed. I get the error on several different hosting accounts and all of the hosts swear blind their config is correct. I have seen multiple threads about this issue and multiple fixes and I am assuming the same issues are still here with 2.7 other than at least the admin panel tells you the post has not been published by tagging it “Missed schedule”

I read somewhere not long ago that this issue with apparent cron server configuration issues would be fixed

Improved, not fixed. 2.7 uses the new HTTP API, which is more adept at actually being able to connect to things (it doesn’t rely entirely on fsockopen anymore), but a broken host is a broken host, and WordPress can’t “fix” what is not WordPress’s problem.

I get the error on several different hosting accounts and all of the hosts swear blind their config is correct.

They are mistaken. The only way the wp-cron jobs can’t run is a) nobody is looking at your site (including you in the admin screen) or b) the site itself is unable to make a connection back to its own URL with wp-cron.php appended to it.

I’m having the same problem. That said, I’ve three different sites all of which use scheduled posting and are located on the same server. Two of them work, one of them doesn’t. What do I need to look at in this case?

update: I installed another instance of WordPress just to test — and that install doesn’t work either…

Now, how can I verify if this is a webserver config issue or not ?

If you make a new post and some “do_pings” events show up in WP-Crontrol and never go away, then it’s a webserver config issue.

You mean any kind of post or a scheduled post ?

No cookie for me: I’ve created a new post and no “do_pings” events showed up in WP-Crontrol. The post is showing as “Missed Schedule”.

Another question: is this an exptected message “Warning: array_merge() [function.array-merge]: Argument #1 is not an array in ..\xadrez\wp-content\plugins\wp-crontrol\wp-crontrol.php on line 290” ?

You mean any kind of post or a scheduled post ?

Regular post, not a scheduled one.

As for the error message, I think WP-Crontrol just has some minor issues. I usually turn off the PHP Warnings on my production sites though.

I’ve posted a few regular posts, just one do-ping showed up and it is still there. Is it normal ?
Do you know where I can find the webserver requirements/specification for WP ? I will try to check with my provider but need to understand the rationale behind the requirement before talking to them.