AWS Invalidations

  • Resolved JordanMcCrary

    (@jordanmccrary)


    7 years ago

    We updated to the most recent version 0.9.7.3 & changed from Generic Mirror back to AWS CloudFront as it seems those bugs were fixed in updates – but we are still facing the incorrect invalidation issue.

    I changed back to “Generic Mirror” but the problem persists.

    We want to upgrade to the paid version of the plugin for FSD & Fragment Caching but with the problem still causing $1000s in overages, that’s out of the question.

    Is there something else we can do to fix this? I love W3TC but this bug is going to put us out of business…

Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    7 years ago

    Hello @jordanmccrary,

    In Performance>CDN, advanced sub-box the first option is “Only purge CDN manually”. Enable that option.
    We built that because of the problems with invalidation requests on CloudFront causing huge bills. If it’s enabled, you can click the purge CDN button in W3 Total Cache to send invalidation requests, otherwise, all changes will be detected automatically and an invalidation request will be sent immediately.

Viewing 1 replies (of 1 total)

The topic ‘AWS Invalidations’ is closed to new replies.