ShoutMeLoud – Shouters Who Inspire

Superlinks
≡ Menu
≡ Menu

WordPress Missed schedule problem [Solved]

bluehost
WordPress Missed schedule problem [Solved]

So my last post was about missed schedule problem in wordpress 2.9. Because of this problem I missed posting many posts which were scheduled.

After looking into lots of solution in wordpress support forum community , I realize the problem is with WordPress cron jobs. And there is a quick and easy solution to this problem. but to resolve this issue we need to edit our cron.php file which is into wp-includes folder.

Make sure before you start editing your cron file , take a backup of this file . So that while editing if you make any mistake, you can always revert back to previous state.

To start with fixing missed schedule problem , access your wordpress files using any FTP client. Download cron.php file from wp-includes folder.

Look for line

wp_remote_post( $cron_url, array(‘timeout’ => 0.01, ‘blocking’ => false, ‘sslverify’ => apply_filters(‘https_local_ssl_verify’, true)) );

wp thumb Change the timeout to some higher value . In my case I changed it to 10 sec, by simply changing

‘timeout’ => 10, ‘blocking’ => false

<Source>

I’m sure many of you who are facing this problem, will find this solution very useful and will make most out of WordPress scheduling feature.

Do let us know if you find any other bug in WordPress 2.9.

{ 14 comments… add one }

  • ipad apps

    Will this work with 3.0 version (current WP version is 3.0.1, haven’t updated yet)? 2 minutes elapsed now, red text “Missed schedule”.

    Thanks in advanced.

    Reply
  • Mark

    By “solved” you mean “still happening in 2.9.2″ :P

    Reply
  • Ryan

    Didn’t work for me. Our case is an issue with media temple dv hosting though it seems.

    Reply
  • Kevin

    No, this solution did not solve my issue either. :-(

    Reply
  • Professional Copywriter

    Has anyone implemented this and still found it hasn’t worked? I’m a little annoyed *shakes fist in the air*

    Reply
  • green

    not solved my problem

    Reply
    • Glupais

      Found solution. I added a record 127.0.0.1 domain.com to /etc/hosts file. I had a routing problems.

      Reply
  • letianmoon

    Thank you for sharing it is really useflu.

    Reply
  • Ari Herzog

    Thanks for sharing this information, as I just experienced it!

    Reply
  • Eating Disorders

    thank you for this tutorial, now all my problem is solve

    Reply
  • MQ Hidayat

    Thanks for this info.
    I see this problem until 2.8 ver.

    Reply
  • Timo

    Thanks! Worked fine with changing the value from 0.01 -> 1.
    And have a great Christmas!

    Reply
  • HackIdeas

    Thx Harsh. Will sure try if this works.

    Reply
  • Sunil Jain

    Uff Thank god :) At last i found some solution
    Thanks Harsh :) :)

    Reply

Leave a Comment