Missed Schedule

I’ve tried the patch below but…

@intended
I’ve just tried disabling curl, as proposed here:

when i first made those changes, it still did not work at first. so i followed the instructions at the next link and i was all set to go

https://trac.www.ads-software.com/ticket/8590

Now let’s see if this does the trick…

no cookie for me. Still missing all scheduled posts.

I upgraded from 2.6 to 2.7 on three of my five WP sites. All the 2.7 upgrades are not scheduling. Even if I manually go to the wp-cron page, the scheduled posts and actions are not executed.

All schedules were working perfectly before the upgrade. The remaining two 2.6 sites are working perfectly.

I am running Windows Server 2003, with latest MySQL, and IIS.

I am having the same problem. I have 6 sites and it’s only happening on one of them.

What gives?

Someone PLEASE figure out this problem!

If it’s any help, it didn’t start happening until I switched hosting servers from ANSHosting to HostGator. I can’t tell what the difference is if it’s like php or something. I don’t know a lot about this stuff so I’m very frustrated!

HELP!!!!!!!!!!

I have the same problem…
So I hope a new release of wordpress will coming soon to fix this problem.

If you can schedule a “cron job” from your server or elsewhere, and you’re comfy with coding, this might help…

1. Make a copy of “wp-cron.php” and name it something else.

2. Under “require_once(‘./wp-load.php’);”, enter the line “echo wp_hash(‘187425’);”, followed by “exit;”.

3. Delete everything below that line, but remember to keep the PHP close code at the bottom.

4. Upload the file to your server and call it from your browser. You’ll see a very long string of gibberish. Copy that. You can (and should) delete the file from your server when done.

5. The address “https://yoursite.com/wp-cron.php?check=xxxx” (where xxxx is that gibberish string) will trigger your site’s scheduler. Since our site typically schedules entries for :00 and :30, I’ve created a cron job that calls that address at :01 and :31. Seems to work, knock on wood.

Normally your own site calls that address when needed. I don’t know why it’s not working on 2.7. There’s some talk it might be a “curl” problem, but if I understand how the new http.php API works, I don’t know whether that’s the case — I’ve been able to update plugins with 2.7, and presumably they use the same method.

Other than that, I like what I’m seeing with the new version. But there’s always a catch…

And in related news…

https://www.ads-software.com/support/topic/228357

“I had to edit wp-includes/cron.php to replace wp_remote_post with wp_remote_get.”

I don’t know whether the WP cron function calling a “post” instead of a “get” is the heart of the problem, but it’s a notable change.

Is there anyone from a host provider reading this thread??

Does this issue get raised any further than the 1 person in customer support who religiously tells me to check the WP forums?

Can the person who suggested ‘server settings’ please elaborate. This would at least give me some concrete information to check with my host.

Just upgraded (thank you Matt) from 2.5 where I had this problem to 2.7. And I still have the problem.

I sent this forum page to my host provider and asked if they read if. Here’s the reply,

“Yes I did see the link but we would not go on a support forum and post there as a company. This is WordPress’s software not ours, I’m afraid we did not code this nor do we know what their code is trying to do! There’s thousands of software out there that customers install and want to use not just WordPress, it’s simply impossible for us to support all 3rd party software.

They should be asking you the questions about our servers, which if you forward to us we’ll be happy to answer. We don’t know what their questions will be though :)”

I understand that they can’t post as a company but can anyone tell me the correct questions to ask about servers?!

I’m with Heartinternet in case anyone’s wondering.

Tell them that a file in WordPress, wp-cron.php tries to use cURL to connect back your domain. Ask them if mod_security is blocking you; also ask them if their DNS configuration is set up correctly.

Schedule a post to be published at a particular time. Keep track of the time, and refresh a blog page within a minute or two after the post is scheduled to appear. Give your hosting support the exact time that you accessed your blog; they should be able to look at server error logs to see what is going on. The cron imitator calls itself with a query string. The file is https://yourdomain.com/wp-cron.php.

P.S. You might also point out that you weren’t expecting them to post on the support forum – just read it to see if they had any ideas as to why their server configuration isn’t performing as it should.

Since upgrading to 2.7 I experience the same. Previously (from 2.1-2.6.3) it was AOK.

I see this as an important tool as I can’t be at my desk all the time.

I hope this is getting the attention it deserves for 2.7.1, as it is clearly at 2.7 bug, blaming hosts/servers (or asking them to change their setups) is not really tenable.

Thanks for your ongoing improvement!
Bill

This doesn’t fix the problem, but at least it will publish the post without having to manually edit the DB…

If you try to _edit_ the posts which have missed schedule, there’s no UI to actually publish them. However, if you do a “Quick Edit” instead, there _is_ UI for publishing the posts.

This is what I’m having to do until a fix is found. cUrl is enabled on my server, but the posts still show up as “missed schedule”.

Interesting comment from Dennis at https://trac.www.ads-software.com/ticket/8737#comment:2

Just FYI, every customer of mine who was complaining about future posts not getting published (or pings not happening, for that matter) turned out to have a HUGE ping list. And indeed, in this case, the cron job just… stopped on the ping list. Dropping the ping list to something more reasonable (one or two sites) fixed things up.

I am also with heart internet and have a long support thread based on the fact that outgoing pingbacks and trackbacks do not work along with the update services ping, I have just tested a scheduled post and this does not work either.

Are all of these issues related to wp-cron not being able to connect back to my server?

@helzy – have you got any further with Heart Internet?

Hey Everyone,

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.

I know this isn’t a perfect fix but if it helps someone with this problem then I hope it works for you.

Cheers ??

jadebydesign – Confirmed, this does work. I copied the wp-cron.php and cron.php files from my 2.6 blogs to my 2.7 blogs. Since I am running on Windows Server 2003, I had to do an iisreset. After the reset, all blogs kicked of scheduled tasks and past scheduled tasks.

Thanks jadebydesign