Why your plugin is loading Google Fonts from CDN when it is not used?

Hi @dziudek

The behaviour you’re experiencing is likely due to the way your theme is designed and developed. I suggest contacting your theme developer so that they can use Stripe’s hooks to use custom fonts or disable Google fonts.

In the meantime, you may consider using a plugin that disables Google Fonts, or manually dequeue the font in your child theme’s functions.php file.

I hope this provides some clarity on the matter. If you have any other questions or need further assistance, please don’t hesitate to ask.

Hi @shameemreza

Sorry but this problem is for 100% connected with your plugin not with our theme. This problem occurs only when using new checkout experience (for old checkout experience there was no issues like this).

Also I have checked code of your plugin and it contains references to Google Fonts in JS code.
Additionally – the request to Google Fonts is definitely initialized by your plugin – that’s why I am contacting with you. Simple test – when Stripe payment gateway is not available, the Google Fonts request is not called. It appears only when I have Stripe payment gateway visible.

Additionally Google Fonts are retrieved by window.fetch function in your fingerprinting script

Hi @dziudek

The team is already aware of this issue: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2489

At the time being, we can’t give you an estimate for when the team will look into or fix the issue, as bug reports are prioritized based on a few criteria. Please subscribe to the GitHub issue if you’d like to receive updates.

Meanwhile, as I suggested, you can discuss with your theme developer so they can hook into Stripe’s hooks.

I wish I could help more, but hopefully, this gets you going in the right direction to get some further insight.

Hi @shameemreza ,

Unfortunately hooks which I have found also are not helping with solving the issue – that’s why I have reported it ?? Trust me – I have tried to solve this problem by myself before reporting it ?? Usually I report issues which cannot be solved even with programmer knowledge due plugin architecture

Hi Tomasz, @dziudek,

Unfortunately hooks which I have found also are not helping with solving the issue – that’s why I have reported it ?? Trust me – I have tried to solve this problem by myself before reporting it ?? Usually I report issues which cannot be solved even with programmer knowledge due plugin architecture

Thank you for the update. It’s great that you take the proactive approach to trying to figure out those kinds of issues on your own since you’re a programmer. I see you’re active on the GitHub link my colleague shared, you’ll be able to check in with the developers directly in there to learn more.

You can also ask for insight related to this on either the?WooCommerce Advanced Facebook group?or the?WooCommerce Community Slack. Many of our developers hang out there and will be able to offer insights into your question. Additional options to consider:

• A local web developer
• A freelance developer (Upwork, Fiverr, etc)
• Codeable.io
• WooExperts

I wish I could help more, but hopefully, this gets you going in the right direction to get some further insight/information.

Thanks!
-OP