• Resolved natrolability

    (@natrolability)


    Firstly this plugin has been amazing and exactly what i needed to pre-warm key pages from my sitemap.

    However, somewhere between version 1.2.5 and 1.3.2 the scheduled warmup has stopped working. Will only run manually.

    I therefore reverted back to version 1.2.5 and the schedulder is working again so not site related.

    Please can you fix this as want to keep aligned to latest version.

    I’ve exported my settings below in case this helps with any troubleshooting.

    {“cache-warmer-setting-depth”:”1″,”cache-warmer-setting-user-agents”:[{“value”:”Mozilla\/5.0 (X11; Linux x86_64) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/119.0.0.0 Safari\/537.36″},{“value”:”Mozilla\/5.0 (iPhone; CPU iPhone OS 15_0 like Mac OS X) AppleWebKit\/605.1.15 (KHTML, like Gecko) Version\/15.0 Mobile\/15E148 Safari\/604.1″}],”cache-warmer-setting-cookies”:[],”cache-warmer-setting-interval”:”30″,”cache-warmer-setting-url-params”:[],”cache-warmer-setting-request-headers”:[],”cache-warmer-setting-entry-points”:[{“url”:”https:\/\/boulderflash.com\/page-sitemap.xml”},{“url”:”https:\/\/boulderflash.com\/product_cat-sitemap.xml”},{“url”:”https:\/\/boulderflash.com\/category-sitemap.xml”},{“url”:”https:\/\/boulderflash.com\/post-sitemap.xml”}],”cache-warmer-setting-timeout”:”30″,”cache-warmer-setting-visit-second-time-without-url-params”:”null”,”cache-warmer-setting-visit-second-time-without-cookies”:”null”,”cache-warmer-setting-rewrite-to-https”:”null”,”cache-warmer-setting-speed-limit”:”1000″,”cache-warmer-setting-exclude-pages-with-warmed-canonical”:”1″,”cache-warmer-setting-for-how-many-days-to-keep-the-logs”:”1″,”cache-warmer-setting-assets-preloading-scripts”:”null”,”cache-warmer-setting-assets-preloading-styles”:”null”,”cache-warmer-setting-assets-preloading-images”:”null”,”cache-warmer-setting-assets-preloading-fonts”:”null”,”cache-warmer-setting-warm-up-posts”:”null”,”cache-warmer-setting-posts-warming-enqueue-interval”:”3″,”cache-warmer-setting-external-warmer-license-key”:””,”cache-warmer-setting-excluded-pages”:[“checkout”,”basket”,”https:\/\/boulderflash.com\/category\/news\/”],”cache-warmer-setting-add-this-site-all-public-posts”:”null”,”cache-warmer-setting-add-entry-point-sites-sitemaps”:”null”,”cache-warmer-setting-use-object-cache”:”null”,”cache-warmer-setting-excluded-pages-use-regex-match”:”null”}

    Thanks

Viewing 12 replies - 1 through 12 (of 12 total)
  • I have the same problem on several WP installations on different hostings.

    Plugin Author TMM Technology

    (@tmmtechnology)

    @natrolability @dietlin

    Can you try updating to the newer version. I think I fixed it.

    Sorry for the inconvenience.

    Thread Starter natrolability

    (@natrolability)

    Thanks. Just updated to version 1.3.4 and it caused a critical error on my website so had to revert back to version 1.2.5 again. below is the error message in my logs if this helps:


    2024/10/19 18:15:54 [error] 63763#63763: *122300 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Class "WP_CLI" not found in /www/boulderflash_466/public/wp-content/plugins/cache-warmer/src/class-extend-wp-cli.php:21

    Stack trace:

    #0 /www/boulderflash_466/public/wp-content/plugins/cache-warmer/cache-warmer.php(170): Cache_Warmer\Extend_WP_CLI->__construct()

    #1 /www/boulderflash_466/public/wp-includes/class-wp-hook.php(324): Cache_Warmer\Cache_Warmer->Cache_Warmer\{closure}('')

    #2 /www/boulderflash_466/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)

    #3 /www/boulderflash_466/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

    #4 /www/boulderflash_466/public/wp-settings.php(700): do_action('init')

    #5 /www/boulderflash_466/public/wp-config.php(89): require_once('/www/boulderfla...')

    #6 /www/boulderflash_466/public/wp-load.php(50): require_once('/www/boulderfla...')

    #7 /www/boulderflash_466/public/wp-blog-header.php(13): require_once('/www/boulderfla...')

    #8 /www/boulderflash_466/public/index.php(17): require('/" while reading response header from upstream, client: 217.113.194.84, server: boulderflash.com, request: "GET /flexibility-and-warmup/?add-to-cart=261897 HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.1-fpm-boulderflash.sock:", host: "boulderflash.com:43513"
    fidoboy

    (@fidoboy)

    I’m having the same issue. The warming process is not being scheduled anymore

    Plugin Author TMM Technology

    (@tmmtechnology)

    @fidoboy @natrolability I think I fixed the crash and warmings scheduling. Sorry for the crash. I changed my testing routine.

    Thread Starter natrolability

    (@natrolability)

    Thanks, appreciate the crash fix. The issue now with latest version is that the scheduler is now only running every 4 hours (even though set to every 30 minutes in setttings).

    In scheduled actions I can now only see the hook “cache_warmer_fix_missing_intervals” with a recurrence of every 4 hours in pending actions after i run the cache manually for the first time.

    I will to revert back to old version again as was running every 15 minutes before recent updates.

    Thanks again for your help with this.

    Thread Starter natrolability

    (@natrolability)

    In case it helps, in version 1.2.5 of the plugin I see 3 hooks in total after running the warmer manually.

    The 2 additional hooks in scheduled actions that I do not see in the latest version of the plugin 1.3.6 are ‘cache_warmer_process_posts_enqueue’ and ‘cache_warmer_process_interval’. The only hook I see in the latest version is ‘cache_warmer_fix_missing_intervals’.

    The scheduler is working in version 1.2.5.

    Thanks again.

    In my case there is scheduled actions in WordPress in the name of Cache Warmer. My cache_warmer_process_interval (I also have cache_warmer_fix_missing_intervals and cache_warmer_clear_old_actions) is scheduled every 22 hours, but the process is not being started. After I launch the initial warming process manually there is no more being created automatically.

    • This reply was modified 3 weeks, 5 days ago by fidoboy.
    • This reply was modified 3 weeks, 5 days ago by fidoboy.

    I noticed in failed actions log this message:

    action failed via Async Request: Unidentified action 12741217: we were unable to mark this action as having completed. It may may have been deleted by another process.

    The hook is cache_warmer_process. May be it helps.

    • This reply was modified 3 weeks, 4 days ago by fidoboy.
    Plugin Author TMM Technology

    (@tmmtechnology)

    @fidoboy were you able to solve the scheduling issue?

    Could you go to scheduled actions -> Pending and then look up for “cache_warmer_process_interval” interval?

    UPD. I will fix it. I know what’s the problem.

    Plugin Author TMM Technology

    (@tmmtechnology)

    @natrolability @fidoboy @dietlin Can you try the new version 1.3.7? I think I fixed the issue there.

    Version 1.3.6 was already working fine for me. But it was patched by Patchman due to a vulnerability of the “code injection” type here:

    …/wp-content/plugins/cache-warmer/vendor/wp-cli/wp-cli/bundle/rmccue/requests/src/Iri.php

Viewing 12 replies - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.