Font CDN issue

  • Resolved dev

    (@devksec)


    3 years, 9 months ago

    Hello,

    So we have Total cache setup on a multisite installation. Two of the subsites use a similar font pack mandated by their theme. All files are uploaded to a cloudfront CDN loaded from an S3 bucket (setup in total cache).

    On one of the subsites, a key font regularly gets a CORS errors while all of the other fonts are fine. Normally we have to purge that one font from the CDN to resolve however it keeps coming back.

    Now when we try to clear the font we get the following error: Not a valid retry configuration argument.

    How can we resolve this issue with the font CORS problem ?

    Many thanks

Viewing 5 replies - 16 through 20 (of 20 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @devksec

    Thank you for the information.
    Just to confirm, the only way to make this work is to disable WP-Activity logger plugin?
    Thanks!

    Thread Starter dev

    (@devksec)

    This is correct.

    They are also aware of this as well but we’ve had to disable one plugin to have the other work currently.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @devksec

    We tried to limit the number of requests when w3tc loads aws library and it happens only when interactions with aws are required.
    The solution provided in the previous post should work only if the other project using the AWS library does the same.
    And if I am not mistaking this is the issue you are referring to?
    Thanks!

    Thread Starter dev

    (@devksec)

    So when using the workaround to exclude the w3tc awslibs via wp-config, it results in a “‘Aws\\S3\\S3Client’ not found ” error and the cloudfront CDN breaks as a result.

    No that’s a separate issue entirely. We have a temp-patched version of activity logger which excludes the AWS libs and now does not conflict with w3tc. Our issue was raised with the devs directly not via the WP forum.

    It’s definitely being caused by an AWS library conflict.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @devksec

    Thank you for the information and I am glad you managed to resolve this with the other plugin.
    Thanks!

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Font CDN issue’ is closed to new replies.