Yoast 16.1 triggers hundreds of CDN invalidation with w3tc

Update: it also happens on a brand new instance of WP. Nothing else then WP + W3tc (CDN Cloudfront) + Yoast, all of them up to date.

Hi @marcocanestrari,

Thanks for reporting the issue. We haven’t received other reports of a similar problem involving Yoast SEO and W3TC.

Can you give us more details about what requests are being made or an example URL where this problem is happening?

Have you found any JavaScript errors in the browser’s Console or under the Network tabs?

It may also help to check your PHP error log for any error messages. You can do this by enabling WordPress debugging or contact your web host.

Ok will perform those checks ASAP

Hi,

Thanks for getting back to us.

If you can perform a conflict check (default WP theme and only Yoast SEO plugin enabled) and check how to reproduce the issue, this would be helpful so we can understand and try to reproduce it from our end — https://yoast.com/help/how-to-check-for-plugin-conflicts/

Hello,

while I couldn’t identify any conflicts, I was able to reproduce the issue on a brand new WP site.

WP 5.7.1
Yoast 16.1.*
W3TC 2.1.1 with Cloudfront Full Site CDN activated

the CloudFront invalidation is triggered:
– twice when activating Yoast
– once each time I save from General > Features but only in any settings changes.

No PHP errors or warnings are logged.

On a production website this is triggered hundreds of times a minutes, so it’s almost impossible to understand how exactly.

Hope this helps you to help me ??

Hi,

We understand you are getting these invalidation requests on a fresh install and with only Yoast SEO and W3TC enabled. Did you use a default WP theme such as Twenty Twenty?

Perhaps also installing the extension plugin that W3TC also offers to work well with Yoast SEO might help.

Unfortunately, we haven’t received any other reports from other users on this, and since there are no PHP errors or warnings, it might be difficult to reproduce this reliably. If it still continues to occur, we recommend opening a bug report, detailing each specific step and the specific set-up — https://yoast.com/help/how-to-write-a-good-bug-report/

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.