Should DISABLE_WP_CRON set to true for plugin to work?

  • Resolved warrior7089

    (@warrior7089)


    5 years, 7 months ago

    1) Is it correct that one needs to delete old caches manually after running wp fvm purge if DISABLE_WP_CRON is set to true?
    Is is the only issue, disabled WP_CRON causes?

    I’ve noticed here:

    The new cache will be generated as needed, but the old files will stay on the server for another 3 months, until they are deleted by a daily cronjob, which will give you plenty of time for your old cache to expire.

    2) There are numerous fastvelocity_purge_old_cron_event in the output of wp cron event list. What is the meaning of these events? Should they be generated if WP_CRON is disabled?

Viewing 1 replies (of 1 total)
  • Plugin Author Raul P.

    (@alignak)

    Hi,

    a) You should never disable wp_cron, since that’s needed for a lot of things, including scheduled posts in the future, auto cleaning, transients expiration, etc.

    You can add the DISABLE_WP_CRON flag, provided you create a server side cronjob running at least, every 30 minutes. This should ideally run every 5 minutes, especially if it’s a woocommerce shop… or else, orders may be stuck.

    wget -q -O - https://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

    Once you have a manual, working cronjob, you don’t need to worry about fvm or anything else.

    2) Just make sure you have the latest FVM version, because a few versions back it was creating too many of them.

    You can delete those cronjobs from the database and leave only one, daily cronjob.

    They are not being generated… they were scheduled and somehow, not deleted.

    In doubt, disable the option to preserve the settings, uninstall FVM and reinstall it again. That should normalize the cronjobs.

Viewing 1 replies (of 1 total)
  • The topic ‘Should DISABLE_WP_CRON set to true for plugin to work?’ is closed to new replies.