WordPress.org

Ready to get started?Download WordPress

Forums

W3 Total Cache
[resolved] Minified files not served via CDN after cache refresh (3 posts)

  1. Ben Balter
    Member
    Posted 3 years ago #

    Upon manual refresh of the cache, W3TC attempts to repush minified CSS and JavaScript files to the CDN (S3, in my case), but the transfers fail and end up in the CDN queue because the minified files are already in the CDN ("Object already exists" error). Because the transfers resulted in an error, the minified files do not end up in the rewrite rules and are served locally rather than via the CDN, despite the fact that they exist there.

    Expected: Upon manual cache refresh W3TC will attempt to push files to CDN, if identical files exist, will not attempt to transfer a 2nd time (and will not result in error), and minified files will be properly served by CDN via rewrite rules.

    Actual: Upon manual cache refresh W3TC attempts to push files to CDN, if identical files exist, the transfer results in an error (and is placed int he queue) and files are served locally (although manual replacing the local domain with the CDN domain properly serves the files).

    Temporary Fix: Enable Force overwrite (but this is not desirable for production as it overwrites files that need not be overwritten thus making unnecessary calls.), or modify the CSS/JS files, thus forcing a transfer to the CDN.

    Perhaps either A: force overwrite on manual refresh, or B: prevent the transfer from erring out and ending up in the queue if an identical file already exists. I cannot confirm that this problem persists with the regularly transfer modified files option, but can confirm that enabling the option does not resolve the problem.

    (Preview mode is disabled in my case, and the transfer queue has been emptied.)

  2. Frederick Townes
    Member
    Plugin Author

    Posted 3 years ago #

    Can you try the development version of the plugin which uses a later version of the S3 library?

  3. Ben Balter
    Member
    Posted 3 years ago #

    I can confirm that the problem listed above is, in fact, resolved in the development version -- thanks for all your help!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic