Preload doesn't work due to wp-cron parameter

  • Hi,

    Using WP 4.1 and WP Super Cache 1.4.2 the ‘Preload’ functionality doesn’t work for me. The errors in the debug file are the following:

    12:46:50 /wp-cron.php?doing_wp_cron=1420030009.7603640556335449218750 In WP Cache Phase 2
12:46:50 /wp-cron.php?doing_wp_cron=1420030009.7603640556335449218750 Setting up WordPress actions
12:46:50 /wp-cron.php?doing_wp_cron=1420030009.7603640556335449218750 Supercache caching disabled. Only using wp-cache. Non empty GET request. Array
(
    [doing_wp_cron] => 1420030009.7603640556335449218750
)

12:46:50 /wp-cron.php?doing_wp_cron=1420030009.7603640556335449218750 Created output buffer
12:46:50 /wp-cron.php?doing_wp_cron=1420030009.7603640556335449218750 Not caching POST request.
12:46:50 /wp-cron.php?doing_wp_cron=1420030009.7603640556335449218750 wp_cache_maybe_dynamic: returned $buffer

    As suggested in the FAQ page, I’ve used Cron View to verify the cron jobs. Those are all correct. I have no other cron problems.

    I’ve searched the forum and internet, but could not find similar topics. I’ve also disabled other plugins but that did not help.

    For some reason, WP Super Cache’s cron jobs are called with a parameter (perhaps by itself?) which cause the preload to fail.

    Who has an idea what I can try to fix this?

    Thanks in advance for any suggestions,

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter hki429

    (@hki429)

    My webhost examined this case for me (with logging in to wp-admin and all) but couldn’t find a cause for it. They suggest I contact the plugin developers for this; so hopefully someone responds. ??

    Thread Starter hki429

    (@hki429)

    More info:

    * There are no errors in the PHP error_log file.

    * The error is triggered by WordPress executing its cron job, which as I understand happens every so often when a new page view is registered (so not on a schedule).

    * My permalinks are: /%category%/%postname%/

    * The error in the debug log seems to be triggered by this line (on GitHub). But commenting out that line does not let the operation succeed (which makes sense; otherwise it would be an empty error check).

    * As mentioned, my webhost couldn’t find errors on their side, suggesting that it is caused by the plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Preload doesn't work due to wp-cron parameter’ is closed to new replies.