Viewing 5 replies - 1 through 5 (of 5 total)
  • I believe the check is set to run twice a day at 7am/7pm local time (or whenever the WordPress cron is triggered after that due time) but it may be there is some additional “throttling” that further controls when any individual site might get the update so as not cause an avalanche of update requests – I’m sure one of the experts will confirm/deny/explain if that is or isn’t the case 🙂

    But your WordPress cron _must_ be functional otherwise the check simply will not be executed in the first place – so you should verify that your scheduled tasks are executing as required, this is something that the plugin does not currently test and verify.

    If you are not sure you might use something like the WP Crontrol plugin that will let you look at the WordPress cron table and see what tasks are queued, when is their next scheduled run time (so you can check for stuck/overdue tasks) and do other cron related stuff.

    Thread Starter hanheg

    (@hanheg)

    Thanks for your response. I looked at it with wp crontrol and it shows a cron schedule for daily, twicedaily and hourly. So that should be allright?
    Also, I use wp-cron for scheduled backups and that works fine.

    Is there perhaps something really obvious I overlooked? Like, do I have to add some setting to wp-config perhaps as it is an existing wp install, not a fresh wp 3.7 install?

    In that case it probably is your language issue as per a quote from a make.wordpress.org topic on this:

    “Localised (non-english) installs are currently not receiving Background Updates.

    3.7.1 Background updates will be enabled for localised builds shortly, there’s just been some unexpected WordPress.org infrastructure work that needs to happen first.

    They’ll be enabled in the near future (next few days for sure) but in the meantime you can either update manually, or, if you’re not being affected by any of the bugs fixed in it (there’s no security fixes in this release) simply wait a few extra days for it to kick in.”

    This was posted 31st October so I guess whether you wait for the auto update that should happen in the next few days or take the update manually depends on whether there is actually anything in the update you actually need.

    Thread Starter hanheg

    (@hanheg)

    Hi Dr Protocols,
    I missed that. I’ll wait a bit than. I’m interested in seeing the background update happen 🙂
    Thanks a lot for letting me know!

    Thread Starter hanheg

    (@hanheg)

    Hi, I just got the message that the site is updated now.
    Perfect, that makes me smile 🙂

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Site is ready for automatic update but it doesn't update’ is closed to new replies.