• Resolved racosgrave

    (@racosgrave)


    In reference to this post
    https://www.ads-software.com/support/topic/page-cache-white-screen-wp5-2-3/page/2/

    I am experiencing the same thing on my homepage which is constantly flooded with requests (presumably HEAD requests). It seems when the cache is invalidated (using Redis for Page Cache…and pretty much every cache) and a “HEAD” request is the first one after the invalidation the cached page shows a portion of our header and thats it.

    This triggers one of my uptime monitors since text it is looking for is not present. To which I rush in and purge the Redis Cache and (unknowingly) was the first hit to the page which caches the page correctly until the next invalidation.

    I am unsure if this issue was eventually resolved or how? My next step is to goto w3tc-config/master.php and change the value of pgcache.reject.request_head": false, to true. As the author noted…will this change be overwritten at some point?

    For example:

    • When the plugin is updated
    • When a setting on the Page Cache is changed (noting that this field is not in view for Redis cache and is disabled when using Disk Cache Enhanced)

    Please Advise
    Thanks!

    • This topic was modified 3 years, 6 months ago by racosgrave.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @racosgrave

    I am sorry about the issue you are experiencing and I am happy to help!
    The W3 Total Cache generates those rules only in compatibility mode.
    However, the compatibility mode option is shown only when disk-enhanced is used and you switched to something else.
    This may affect browser cache rules historically.
    Can you please switch the Page cache method to disk enhanced, save all settings and purge the cache and share the screenshot of the Performance>Page Cache>Advanced section?
    Thanks!

    Thread Starter racosgrave

    (@racosgrave)

    Even with that change, it still happened on pages that were pinged with HEAD requests or robots. I have gone ahead and switched to Disk Enhanced for Page Cache in the hopes that fixes it (I would rather use Redis but I’d really rather my pages to resolve correctly ??

    Here https://ibb.co/c32rMWJ is a screenshot of the Advanced Section of Page Cache after switching to Disk Enhanced, as noted in the other post…This input is disabled

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @racosgrave

    Thank you for the info. As I’ve mentioned, this may affect browser cache rules historically.
    Try to completely remove and re-install W3 Total Cache:
    1. Purge Cache
    2. Deactivate and Delete Plugin
    3. Check .htaccess File (make backup)
    W3TC will create many directives in .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
    Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
    4. Delete wp-content files and folders
    – cache folder
    – w3tc-config folder
    – object-cache.php (if exists)
    – advanced-cache.php (if exists)
    – db.php (if exists)
    – upgrade folder
    – delete w3-total-cache folder in wp-content/plugins/ (if exists)
    5. Delete Cached Files from CDN (if using CDN)
    Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    6. Go to your wp dashboard and re-install W3 Total Cache

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Page Cache White Screen’ is closed to new replies.