Asset opimisation causing http issues for fonts

  • Resolved katmacau

    (@katmacau)


    4 years, 6 months ago

    Hi Hummingbird. I am continuously having the same issues across multiple sites that I use you plugin on. All different servers, themes, setups, woocommerce, no woocom etc. But all result in the same re-occuring issue where fonts are loaded as http instead of https.

    Whenever I use Auto Asset Optimisation it changes any font file to http instead of https. I then have to change to manual mode and find a fix that way. I’ve tried listing the font files in the exclude list – that helps. But many fonts, such as woocommerce fonts, are included in the actual css file. So I disable it for that file so the font reference doesnt muck with http issues. But then that file is not optimised.

    This as you can imagine is a pain staking process, especially on sites which I have inherited and not initially built.

    My question is – is there a way to disable asset optimisation for ALL font references? Have you seen this issue? Do you have any tips on fixing it?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    4 years, 6 months ago

    Hi @katmacau

    Sorry to hear you are having this issue.

    The best approach is to replicate it on our end so we can fix it on the plugin.

    I don’t remember this issue being reported as a bug, we had a case in the past but it was related to WP calling the HTTP on enqueue process which Hummingbird uses to compress the files.

    You can try this script:

    https://gist.github.com/patrickfreitasdev/e8092a06a700e194ed872b0b6d979076

    To verify if the issue is gone, bit had you noticed any step or any plugin that would be easier to replicate the problem and we can take a closer look?

    Best Regards
    Patrick Freitas

    Thread Starter katmacau

    (@katmacau)

    4 years, 5 months ago

    The main one I have noticed it is with WooCommerce sites. The woo fonts are being changed to http. Its only the font files. The woo css is fine. Doesnt matter on theme or hosts. Same across all. Seems to be when the font is included within the css as an import.

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    4 years, 5 months ago

    Hi @katmacau

    Could you please send me an email to contact@wpmudev.org using this template:

    Subject: “Attn: Patrick Freitas”

    Message: link back to this thread for reference

    Best Regards
    Patrick Freitas

    Thread Starter katmacau

    (@katmacau)

    4 years, 5 months ago

    Thank you. That’s been done now.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Asset opimisation causing http issues for fonts’ is closed to new replies.