Missed Schedule – Scheduled Posts Not Publishing With 2.7

I just noticed that this on my scheduled post from today. I wonder if it has something to do with wp-cache.

I am having the exact same problem. New installation of WordPress 2.7 and regular publishing works fine. Whenever I schedule a post, it gets “missed schedule”.

Got it fixed. Very simple.

I went to my PHP install directory and opened PHP.ini. I then uncommented the following line:

extension=php_curl.dll

Next I did an IIS reset, because my wordpress runs on IIS7. Went back into wp-admin and updated the schedule on just 1 post. That triggered the rest of the posts to run their schedules. All good now!

This happens to me too. I live on scheduling so it hurts! My host doesn’t give me the option to go in and mess the PHP config though.

I’m having this same problem, plus all my third party scheduling code is not longer working, ie TDO-MF.

I’ve looked at the entries and for the life of me can’t see any difference between the posts that are making it to the site and the ones that aren’t. it’s very annoying to have to babysit the database ??

God this sucks, they need to fix this. I wish they’d work on making stuff work right instead of making it pretty in the dashboard.

Once the damn post gets in this status, you can’t even go back in and post it immediately because there is only an option to put another time in and it misses that time, too.

It’s most likely not the problem of wordpress so they will never “fix” it. For me, it had to do with the IP not resolving to the correct place on my server. Check out the post below for details as this one helped me solve it:

https://busyblogging.com/technical/wordpress-problem-with-scheduled-post-solved/

There are 100s of people having a problem with this. There are several other threads if you search around. I have a full rack of collocated severs and I have root access to every single one of them. The servers run a bare minimum of crapware to reduce conflicts and keep things simple. MySQL, Lighthttpd, PHP and a couple of other things and that’s it. If WP is not working as designed on my servers and 100s of other people’s accounts (most of whom are most likely hosting with webhosts rather than running their own servers, which in turn means they are likely following the more traditional LAMP platform much more than I am) than its WP and not my server that’s broke.

I ditched phpBB because they were constantly playing with the core and breaking stuff. There would be a release and then 10 releases to fix the stuff they should have fixed in the first release but didn’t because they didn’t bother to test properly. They were always worried about how things looked rather than how well they worked. With very few exceptions, anytime developers start focusing on making things pretty, the software’s performance and reliability suffers. I know Web 3.0, AJAX and all that other crap is all the rage. But just like Flash and Shockwave – just because its cool and just because its popular doesn’t mean that it doesn’t suck and doesn’t mean you should adopt it. Worse yet, the end user was always the first beta tester. Its looking like its becoming the same for WP.

Some code monkeys simply don’t understand the meaning or concepts behind terms like stable, production, development, bleeding edge, edge, etc. 2.7 was not ready for release, but they pushed it out anyway. In 2008, we have had how many releases? Too many. So many that I wrote a script to crawl the server and update the 100 and something WP installations that I have running in one shot, since doing it manually was becoming a huge burden on myself and my admin.

Ah well, at least this will be a functional workaround. You might not be able to stop the dog from taking a dump on you, but at least you can clean up after it.

Has anyone tried a cron job using curl or wget (or in the case of HostGator, ‘GET’) to access the index.php every so often? If the scheduled posting is running off of wp-cron, then triggering a pagelaod near the time for the scheduled post – or soon after – may result in the post getting posted appropriately. Then again, if a high-traffic blog (and I mean, a hit a minute during scheduled posting times) is getting this issue, then it’s not going to help, as it’s something else.

Just my idea.

I just spent two days diagnosing an issue like this on my web host (which had been working fine).

In my case, it turned out that the web server wasn’t able to receive HTTP HEAD’s through the Squid proxy in front of it.

WordPress sends an HTTP HEAD to check that wp-cron.php exists before loading it, and that was failing, so it was never running.

You can test this by using the command line curl to send HEAD requests to your site,

curl –head “https://your.site.here.com/blog/wp-cron.php” for example.

If you get any errors back, then ask your web host to investigate.

The other issue is that the WordPress code sends that request to the same URI you use to connect to the blog so it has to be able to talk to itself. Some hosts block outgoing connections from the servers, or don’t set them to be able to route correctly to themselves. That’s harder to check if you don’t have direct access to the server, but you could always ask a host provider to make sure it works.

why we have go to curl php.ini thing ..????

it’s harder for end user ?

So what it comes down to is we have all these hacks in place which seem to be VERY temperamental and HEAVILY dependent on the server environment allowing non-standard things (like a server being able to talk to itself) so people don’t have to set a cron job on the server?

Give me a break. Whole setup is really poor. Just make a file that I can set as a cron and have it do the updating, and add the ability to set cron jobs to the software requirements, at least for that feature set.

You can run cron jobs now, just point to wp-cron.php?

My post was simply to make sure people are aware of what ISP’s can get wrong which block WP talking to itself in the background.

So adding wp-cron.php to the cron cycle will take care of the scheduling issue? Is that what I am hearing?