• Hi,

    I’m just wondering how we can fix / diagnose this issue? We’ve tried the plugin however nothing appears to be flagging up the issue?

    The problem is:
    A plugin has prevented updates by disabling wp_version_check().

    We also have this which we’ve seen…(doesn’t always show so I’m guessing its unrelated?)…

    A scheduled event has failed Performance
    The scheduled event, litespeed_imgoptm_trigger, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

    Any suggestions / help appreciated 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Marius L. J.

    (@clorith)

    Hi,

    Sorry for the late response here, many things going on at once 🙂

    I’ll tackle the last item first, because it’s the easiest, the scheduled events checker is being improved on, as it’s a bit too strict right now (which is why you are only seeing it some times), so if it’s not always there, you can safely ignore that warning.

    As for the wp_version_check() test, do you also have a warning mentioning that “loopbacks” are not working?

    Thread Starter adamrj01

    (@adamrj01)

    No “loopbacks” are on this health report. Just puzzled, it could be a setting we enabled on the hosting perhaps?

    Plugin Author Marius L. J.

    (@clorith)

    It is possible, I know some hosts handle updates for you, and disable the built in WordPress one when they do.

    Hi,

    I’m pulling my hair out because Site Health displays three errors, usually in tandem, consistently on several sites. I’ll say right up front that this doesn’t point, at least entirely, directly to Site Health, but any insights are hugely appreciated while I have any hair left!

    Specific case: In a current site migration in testing (not live), and with just default TwentyNineteen and all plugins disabled, I get these three errors:

    – A plugin has prevented updates by disabling wp_version_check().

    – The scheduled event, itbub_cron_test, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

    – The REST API call gave the following unexpected result: (403) {“code”:”rest_cookie_invalid_nonce”,”message”:”Cookie nonce is invalid”,”data”:{“status”:403}}.

    If I activate WP Crontrol plugin, all wp-cron events show the next run date as being 2 weeks in the past (around the time of first migration). Manually running jobs shows success… but without changing the associated next run date. Another confirmation of the problem is that scheduled posts don’t go live… they just remain in draft.

    My error_log and debug.log are clean. When activated, Wordfence gives clean scan.

    Note that on other sites/tests, some of these messages disappear seemingly by eliminating some combo of plugins that use PHP sessions… but I think I’ve taken this one down to plain vanilla with no love. While I’ve run WP caching in the past on the source site, that is not currently the case and I can’t detect any server caching on LiquidWeb hosting.

    FYI, while I might be considered an advanced user who knows enough about this stuff to make myself dangerous, I’m not at developer level.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘A plugin has prevented updates by disabling wp_version_check().’ is closed to new replies.