Google Fonts Not Showing Inside SP Page Builder (Helix Ultimate 2.2.1 / SP Page Builder 6.1.2) - Question | JoomShaper
Black Friday sale is live with flat 50% OFF. Sale ends soon! Grab your deal now!

Google Fonts Not Showing Inside SP Page Builder (Helix Ultimate 2.2.1 / SP Page Builder 6.1.2)

MI

Mohamed ibrahem

SP Page Builder 6 days ago

Hello Support Team,

I am currently using SP Page Builder Version 6.1.2 along with Helix Ultimate Version 2.2.1.

I have already created and configured the Google Fonts API inside the Helix template settings. The Google Fonts list appears correctly inside the Helix typography settings, and all fonts are displayed there without any issues.

However, the problem is that Google Fonts are not appearing inside SP Page Builder. Although the fonts load properly in the Helix template panel, they do not show up in the font dropdown inside SP Page Builder editor.

Could you please advise how I can resolve this issue and make Google Fonts load properly inside SP Page Builder?

Thank you in advance for your support. Looking forward to your guidance.

Best regards,

0
3 Answers
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 6 days ago #210175

Hello Mohamed ibrahem,

Sorry for the inconvenience you're experiencing. Please be aware that Helix Ultimate and SP Page Builder handle Google Fonts separately. While your fonts may be configured correctly in Helix Ultimate, they need to be individually loaded within SP Page Builder itself.

To add and use Google Fonts in SP Page Builder, please refer to this documentation: SP Page Builder Font Book.

We appreciate your understanding and cooperation.

Best regards

0
MI
Mohamed ibrahem
Accepted Answer
5 days ago #210337

Thank you for the clarification and support. I appreciate your help.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 5 days ago #210338

You're very welcome! We're glad we could assist you. Please don’t hesitate to reach out if you have any further questions or need additional support.

Please marked the issue as solved

0