Missed Schedule

It took me a while to figure it all out… nothing seemed to be working in my case!

but…

The solution posted before; replacing the ‘wp-cron’ and ‘cron’ file is partly working: it’s working for all the ‘new’ scheduled posts (scheduled after the replacement). All the posts which have been scheduled before replacement of those files will still be marked as ‘missed schedule’ in the future.

The (only) solution to avoid that is like chrisgiddings showed: draft and then publish again.

So if you’ve got many posts scheduled, make an export of your WP-blog, replace the cron and wp-cron files, import your blog again!!

Just linking this; https://core.trac.www.ads-software.com/ticket/9388

I am having a similar problem on my server. However, scheduling workings for a blog hosted at:

https://domain.com/blog
https://domain.com/blog2

but fails at both:

https://sub1.domain.com/
https://sub2.domain.com/

All run 2.7.1 and all receive 100s if not 1000s of hits an hour.. Could the PHP settings differ on the subdomains?

Just ran across this thread after a client complained of the same issue today. I logged into their 2.71 blog to examine, but they only have a pending one scheduled for 10 hours from now, so either they manually posted it themselves – or – it’s going to be a problem again tomorrow.

So, at this point, there are apparently still people having this problem on 2.71 – so now what, with no wp-cron to replace?

in my particular case “Missed Schedule” warnings disappeared after a sysadmin synchronized the internal server-set time and the real atomic clock’s time. It was a two minutes discrepancy.

@jadebydesign:

Many thanks!

Your solution works!!!

In case this helps any…

I’ve been running 2.7.1 for a while and scheduled posts were never a problem. Then I switched to a dedicated server, moved my site, and all of a sudden I was getting the orange “Missed Schedule” message. I tried jadebydesign’s solution, but it didn’t work for me. Looking forward to this getting fixed in 2.8!

Oddly, the problem I had with mine after the upgrade was that the post_status (wp_posts table) enum was missing the ‘future’ option.

I modified the post_status enum using the following:

ALTER TABLE wp_posts CHANGE post_status post_status ENUM(‘publish’,’draft’,’private’,’static’,’object’,’attachment’,’future’) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL DEFAULT ‘publish’

via phpmyadmin

posts are now appearing in the list of editable posts, and all scheduled posts are now appearing on time.

Cheers,

Laethyn

How I fixed my missed schedule problem, works fine now.

My blog was effected by the new WordPress wp-cron.php internal cron system. There are two ways to get around this… a) Install a plugin that will trigger wp-cron every so often (although I do not recommend this). b) Set up a cron job to load your blog every so often. Personally, on my blogs, I use a cron job to load them once per hour. This ensures that wp-cron will trigger at least once per hour. The easiest way to set this up would be:
26 */1 * * * /usr/bin/lynx -dump https://www.yourdomain.com > /dev/null

This would access your site once per hour, and will dump the page to /dev/null so you will only receive an e-mail on error.

There was a bug reported, sometime in the past few months, where wp-cron would not trigger properly at times. In other words, if the trigger was too far after the scheduled time, it wouldn’t process.

Hope this helps, it helped my blogs scheduled time problems.

We just started having this problem.

We created our blog ~6 months ago w/ Blogger, then imported directly into WP v2.7.1, but JUST NOW started having this issue, for no reason that is apparent to us.

As suggested in this thread, we tried updating the cron and wp-cron files w/ the ones from v2.6.5, but this did not work.

I am wondering whether this issue was caused by a recent update to a plug-in (and if so, which one?), or something our webhost might’ve changed.

If anyone has ideas, we’d be extremely grateful for help, as we publish in the wee hours of the morning and don’t want to have to do this manually!

For the record, I never did find a solution to this problem with WP 2.7.1. However, upgrading to WP 2.8 did the trick and now scheduling works fine on my site.

Having 2.7.1 and 2.8 on the windows hosting. Problem exists for both cases. Any updates on how to fix that?

The issue still persists on 2.8, the only workable solution so far is to revert back to version 2.6.5 wp_cron.php and wp-includes/cron.php as indicated by Jadedbydesign:

I found a solution to this problem but it’s nothing like what’s been proposed here already. My web host doesn’t allow for changes to php.ini by its users and I know nothing about curl and such.

So to make a long story short I decided to put up a test of WordPress 2.7 on a test domain and I exchanged two files from WordPress 2.7 with two files from the last version of WordPress 2.6.5

The files exchanged on my server were wp-cron.php and cron.php

All I did was log into my FTP and upload the wp-cron.php to my WordPress root and the cron.php had to be uploaded to the folder “wp-includes”.

Not only are my posts publishing on schedule but the 6 posts I had that had “Missed Schedule” were published as well when I refreshed my blog.

hello all.

after I moved my blog (wp 2.8) to a new server I got this issue.
I tried most of the solutions you can find on google searches:

1. use cron files from wp 2.6.5/2.7 -> DOESN’T WORK
2. check the etc/host file -> WAS CORRECT
3. use wp-crontrol -> DOESN’T WORK WELL

what I figured out is that the cron jobs are somehow blocked by PHP Safe Mode setting. I disabled it, and it works now.

But can anyone find the right parameter to change, so I can keep PHP Safe Mode On and schedule my posts as well?

I had a problem with missed posts and found the following plugin which worked!!

Scheduled MIAs

Just copy the code, create a file called mias.php, and put the file in your plugins folder. Active it thru the dashboard and voila!