Viewing 10 replies - 16 through 25 (of 25 total)
  • Thread Starter marco-raaphorst

    (@marco-raaphorst)

    I found that it says:

    The DISABLE_WP_CRON constant is set to true. WP-Cron spawning is disabled.

    I have no idea what is causing it. wp-config is set correctly.

    Hi @marco-raaphorst,

    Thanks for the update! WP Control is a helpful tool for checking scheduled events, so that’s a good step. Feel free to reach out once you’ve had a chance to look through it or if you notice anything unusual.

    Thread Starter marco-raaphorst

    (@marco-raaphorst)

    Well like I mentioned WP Crontrol shows:

    The DISABLE_WP_CRON constant is set to true. WP-Cron spawning is disabled.

    No idea what I should do to solve this.

    Hi @marco-raaphorst,

    Thanks so much for sticking with this and for the detailed updates. I understand how confusing it must be to have DISABLE_WP_CRON showing as true in WP Crontrol while your wp-config.php clearly sets it to ‘false’. That mismatch can definitely be frustrating, especially with past-due actions piling up.

    Since you’re seeing this behavior even though your config file appears correct, here are a few things worth checking next:

    1. Check for whitespace or encoding issues in wp-config.php Open your wp-config.php in a plain-text editor and make sure there are no invisible characters, extra spaces, or hidden BOM (Byte Order Mark) before <?php. These can silently interfere with how constants are read.

      2. Search for conflicting definitions It’s possible another plugin or even a must-use (MU) plugin is redefining DISABLE_WP_CRON somewhere else. Try searching your entire site files (e.g. using the search tool in your code editor or hosting file manager) for this line:

        define('DISABLE_WP_CRON', true);

        If another definition exists, even in a custom plugin or MU plugin, it would override your intended setting.

        3. Temporarily add this line near the top of wp-config.php (just after <?php) for debugging:

          define('DISABLE_WP_CRON', false);

          Adding it as early as possible ensures no other plugin or file redefines it before WordPress boots up.

          4. Clear object cache or disable caching temporarily If you’re using persistent object caching (like Redis or Memcached), there’s a chance this value is cached incorrectly. Try flushing your object cache or temporarily disabling your caching plugin to test.

            Once you’ve tried these steps, reload WP Crontrol and see if the message disappears. If the constant still appears as true, feel free to share a screenshot of your wp-config.php (redacting any sensitive details) and we can take a closer look together.

            Let’s get to the bottom of this!

            Thread Starter marco-raaphorst

            (@marco-raaphorst)

            Nothing works except for:

            3. Temporarily add this line near the top of wp-config.php (just after <?php) for debugging:

            Now the warning ‘The DISABLE_WP_CRON constant is set to true. WP-Cron spawning is disabled.’ disappeared.

            Hi @marco-raaphorst,

            Thank you for your update and for sharing what you’ve tried so far. It seems there might be some misunderstanding: the DISABLE_WP_CRON constant needs to be set to false, not true. If this constant is set to true, it disables WP-Cron.

            Here is what I’ll advise. First check through your wp-config.php file and make sure that line of code doesn’t appear in multiple places. If it does, please delete them and place that code changing it to false just above this text “/* That’s all, stop editing! Happy publishing. */”

            Thread Starter marco-raaphorst

            (@marco-raaphorst)

            I have set it to FALSE indeed in WP-config. This line, which is now at the top of wp-config:

            define(‘DISABLE_WP_CRON’, ‘false’);

            I have scanned all my plugins and that line to set DISABLE_WP_CRON can only be found in wp-config.

            No clue why there’s this error. The only thing that works to solve it is setting it at the beginning of wp-config.

            Hi @marco-raaphorst,

            Thank you for your response and the clarification. I just want to confirm—has the issue been fully resolved, or are there still parts that remain unresolved?

            Could you please restate the outstanding issues so we can keep track of what still needs troubleshooting?

            Thread Starter marco-raaphorst

            (@marco-raaphorst)

            It seems that the errors are now gone.

            So the thing that solved it was doing this (the advice been giving in this threads)

            3. Temporarily add this line near the top of wp-config.php (just after <?php) for debugging:

            define('DISABLE_WP_CRON', false);

            The only thing I don’t know is why I should temporarily add this to wp-config. Wouldn’t it make sense to keep it that way?

            Hi there!

            Thanks for the update—glad to hear the errors are now gone!

            The only thing I don’t know is why I should temporarily add this to wp-config. Wouldn’t it make sense to keep it that way?

            You were advised to temporarily add that line to wp-config.php to help determine whether the issue was related to WP-Cron being disabled. It was meant as a debugging step to see if enabling WP-Cron would resolve the problem.

            Since adding the line solved the issue, it’s perfectly fine to keep it in your wp-config.php file — you don’t need to remove it. This simply ensures that WP-Cron remains enabled and avoids potential conflicts if something else on the site tries to disable it.

          Viewing 10 replies - 16 through 25 (of 25 total)

          The topic ‘I am getting past-due actions’ is closed to new replies.