• Resolved joy0114

    (@joy0114)


    Hi,

    Well, in fact, it’s not really solved:

    For a popup, I switch Typography as “Default”, and the result is:

    99 errors (Content Security Policy) when calling “all” (perhaps) fonts (and variants) we can choose in setting section “Typography”.

    According what you explain to me in my previous topic, I was expecting these calls not to be made.

    Did you experiment this behavior ?

    Thanks a lot .
    Best regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Jair – WPMU DEV Support

    (@wpmudevsupport15)

    Hi @joy0114,

    I hope you are doing well today!

    This was our response in the previous topic, which means those fonts will be fetched from Bunny Fonts CDN and you need to update your Content Security Policy accordingly and allow them if you have a custom one.

    When you use custom fonts it will fetch these from Bunny Fonts CDN which is GDPR compliant. This is why we updated all of our plugins in this matter.

    Kind regards,
    Zafer

    Thread Starter joy0114

    (@joy0114)

    Hi Zafer,

    I understood your answer:
    “If you want to use the same font as the active theme, you just need to use the “Default” option, instead of selecting Custom > Roboto again.”

    The issue is that when I set to “default” for “typography”, my 2 modules (one popup and one embed), ALL possible fonts try to load. And then, lots of efforts and errors.

    I do not want to use Bunny fonts, and unfortunatly it seems the setting “default” for typography, does not prevent loading (or attempts to be precise) fonts from bunny.net

    So I was wondering if you experiment this issue.

    Best regards

    Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @joy0114

    I hope you’re well today!

    Let me take a step back and correct the answer that you were given before:

    if you do not want to use Bunny fonts you actually need to not only switch typography to default but also enable “Vanilla theme”.

    I can see that my colleague asked our Hustle Team about it but apparently there was some slight misunderstanding on our end, causing this entire confusion. I’m sincerely sorry for this.

    The way it works is this:

    – if you don’t have “Vanilla theme” enabled in popup/slide-in (or other module) Appearance settings – it will use one of pre-defined styles;
    – those styles also have some fonts defined and those are fonts from Bunny fonts (previously Google fonts)
    – the difference that switching to “default” typography makes – is that instead of using custom chosen fonts, it only uses those that are defined “by default”

    – if you enable “Vanilla theme” option (and don’t customize typography in Appearance settings) it will actually disable all the pre-defined styling (other than just some “layout” – as in e.g. position of image or button – related parts).

    Only then it will take fonts/colors/etc from your theme.

    It will not load Bunny fonts then. I have tested it and can confirm for sure.

    However, please note that these setting are separate “per module” in Hustle. If you set one module like that, there may be another one loading some Bunny fonts – they would all need to be set this way.

    Furthermore, we are switching all our plugins to Bunny fonts so in future you may also need to do similar changes e.g. to Formiantor forms settings – if you are using it.

    Additionally, you mentioned that it appears to be loading “all” the fonts. This is actually surprising and not expected. I did more testing on this and couldn’t replicate this in any way but there is a possibility that this would be caused by some intense asset optimization. Specificially – if CSS has been in some way optimized and cached before changes were made (and if JS was optimized and/or deferred and cached) it may be involved.

    I would strongly suggest re-running all the asset optimization (JS/CSS/fonts) and clearing all caches after making changes mentioned above.

    Kind regards,
    Adam

    Thread Starter joy0114

    (@joy0114)

    Hi Adam;

    Thank you very much for this very precise and well explained answer !

    Thanks to your answer, I manage to avoid attempts of loading extra fonts.
    A little bit of work on css, but it works !
    And yes, a complete purge of css / js / pages cache, is necessary.

    And, you’re right: this did not concern all fonts… but many variants of one (the one which had to choosen in gui naturally). I’m sorry I was inaccurate and excessive.

    Thanks again for your answer and for your work on this plugin.
    Best regards

    Plugin Support Jair – WPMU DEV Support

    (@wpmudevsupport15)

    Hi again @joy0114,

    We are happy to hear that the issue has been resolved for you.
    Please let us know in case you need further help.

    Kind regards,
    Zafer

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Call to fonts.bunny.net/css – Failure…’ is closed to new replies.