Forums

WordPress › Support » Alpha/Beta

1 2 3 4

Missed Schedule (92 posts)

  1. gumgone
    Member
    Posted 11 months ago #

    How do I go back to the older version of WORDPRESS... as I read all the fools .... like myself ... following in steps to jump off a bridge.. ... WE ARE ALL HAVING THE SAME ISSUE.... all of a sudden ... ???? and it is not wordpress... that is the issue ???/ well ... well....

  2. stelling
    Member
    Posted 11 months ago #

    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

    http://trac.wordpress.org/ticket/8590

    Now let's see if this does the trick...

    no cookie for me. Still missing all scheduled posts.

  3. merlin981
    Member
    Posted 11 months ago #

    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.

  4. delectual
    Member
    Posted 10 months ago #

    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!!!!!!!!!!

  5. binbin
    Member
    Posted 10 months ago #

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

  6. stinque
    Member
    Posted 10 months ago #

    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 "http://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...

  7. stinque
    Member
    Posted 10 months ago #

    And in related news...

    http://wordpress.org/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.

  8. Helzy
    Member
    Posted 10 months ago #

    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.

  9. Helzy
    Member
    Posted 10 months ago #

    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.

  10. stevejohnson
    Member
    Posted 10 months ago #

    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 http://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.

  11. billnanson
    Member
    Posted 10 months ago #

    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

  12. dherren
    Member
    Posted 10 months ago #

    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".

  13. MichaelH
    moderator
    Posted 10 months ago #

    Interesting comment from Dennis at http://trac.wordpress.org/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.

  14. cookeal
    Member
    Posted 10 months ago #

    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?

  15. jadebydesign
    Member
    Posted 10 months ago #

    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 :)

  16. merlin981
    Member
    Posted 10 months ago #

    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

  17. jadebydesign
    Member
    Posted 10 months ago #

    Hi Merlin981,

    I'm glad this solution worked for you :)

    I'm pretty sure the problem is that Wordpress 2.7 has this new line that references "local time" in the wp-cron.php code as well as they changed the length of time to do the job from +30 to zero in 2.7

    It seems to me that if some servers do not match up to Wordpress's "local time" then the length of time to do the cron job set at zero would cause Wordpress to cancel the auto-post. I'm no egghead but that's my best guess at what is happening. I also didn't want to modify my cron files in case I made a mistake so I simply overwrote them as I outlined above and it worked like a charm.

    If anyone wants the fine details of how I hatched this fix I wrote a post about it this morning on my blog at: http://newbloghelp.com/wordpress/wordpress-missed-schedule-future-posts-fix/

    Cheers everyone :)

  18. mafreino
    Member
    Posted 10 months ago #

    I thought I found the solution to this horrible problem but... what jadebydesign suggested... doesn't work for me!!! I don't know why you both got the solution with these two 2.6 version docs... and if I do it I just get the same problem and nothing change... I need to schedule posts!!! =(

  19. thehalogod
    Member
    Posted 10 months ago #

    I am also having issues with this (started a post in the trouble shooting forum before I saw this one)

    http://wordpress.org/support/topic/236454?replies=13

    I really hope that the Wordpress developers will fix this for 2.71. Even if it appears to be affecting a few users and not all. I've never seen any old support threads showing issues with this before...

  20. jadebydesign
    Member
    Posted 10 months ago #

    @mafreino and thehalogod,

    This fix is working for most Wordpress users, maybe you could try checking with your web host you may need to do an iisreset to get this fix to work depending on what sort of server setup you have. You two are only 3 folks who have said this fix isn't working...so I'm wondering about your server setup? Double check your host settings...

  21. thehalogod
    Member
    Posted 10 months ago #

    I pay for a dedicated server and have root access... so what do I need to change?

  22. RobertBrainstorm
    Member
    Posted 10 months ago #

    I am running wordpress on a layer 4 load balanced system. curl and wget cannot access the site and just times out.

    To solve the scheduled posts problems I have had to copy the wp-cron.php file, move it out of the http docs directory and manually create a cron task to run every 5 minutes.

    However my site is still unable to receive pingbacks. I need to do some more research into alternative methods that can be used here and work with load balanced systems, so I will post back what I find!

  23. patdeznuts
    Member
    Posted 9 months ago #

    I had the same issue with this on load balanced wordpress-mu 2.7 install. The server needs to be able to resolve the site name. Added ip address with name of site to host file then restarted apache. Now scheduled posts appear without any issues because wp-cron is called properly.

  24. jpodtbc
    Member
    Posted 9 months ago #

    just to inform everyone:

    2.7.1 appears to solve this bug. though i did NOT upgrade (i am unable for various reasons) i replaced the 2.7 files:
    /wp-cron.php
    /includes/cron.php

    with the ones from the 2.7.1 release and i can totally schedule with no problems now.

  25. minusonebit
    Member
    Posted 9 months ago #

    Well, 2.7.1 surprise, surprise DOES NOT fix the issue. I scheduled a post five minutes in advance after completing the updates, sure enough, it goes to "Missed schedule".

    Also, doing a "Quick Edit" to get the publish now button also does not publish the post. It simply sets it to status of published but it never updates the index page with the new post.

    Goddamn but this is an annoying little bug.

  26. xensen
    Member
    Posted 9 months ago #

    I too still have this problem in 2.7.1. A stupid simple workaround is to change the post status to draft and then change back to publish. It's not very satisfactory but at least it does get the post published. Hope this gets fixed soon!

  27. xensen
    Member
    Posted 9 months ago #

    Jade's workaround seems to fix the problem for me.

  28. eboehnisch
    Member
    Posted 9 months ago #

    Jade's workaround works for me, too. Dear Wordpress developers: Please check what has been changed in includes/cron.php between 2.6 and 2.7 that could break it. It's a really annoying problem because nobody seems to be able to point us to what we need to check on the web server etc.

  29. DJAllyn
    Member
    Posted 9 months ago #

    Scheduling was working fine for me UNTIL I updated to WP 2.7.1.

    The funny thing is, I have two items that are scheduled every day, and only one of them go. This is VERY irritating to me, considering I set my posting up two weeks in advance and everything is supposed to be time-orientated.

    This needs to be fixed soon.

  30. Harvey
    Member
    Posted 9 months ago #

    Oh man. I can't believe this hasn't been fixed from 2.7.0 to 2.7.1...

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags