Okay
  Public Ticket #3604560
self-hosted fonts
Closed

Comments

  •  1
    rendjy started the conversation

    Hi there,

    I have a problem changing the source for the fonts on my homepage. I would like to host the fonts that are currently active - Inconsolata, Open Sans, Unica One and Orbitron myself. I have already uploaded both the ttf and woff2 files and specified the paths to the files. Unfortunately this did not work. Can you please help me to change the source of the font.

  • [deleted] replied

    Hi rendjy,

    Please share your website login credentials with me so I can test this. To safely include your credentials click the Insert Credentials button in the editor toolbar (see how).

  •   rendjy replied privately
  • [deleted] replied

    Sure, if they are Google Fonts, you must go to your Typography > Settings area and enable the Pull Google Fons option (see example).

    This method will download those Google fonts and save them locally on your serversmile.png

    More info: Kalium Typography documentation.

    Have a great day!

  •  1
    rendjy replied

    Thank you very much for your support!

    That worked out well. In the font settings, the source is still Google Fonts. How can I check whether the change really worked and the fonts are now hosted locally on the server?

  • [deleted] replied

    The source shows them as Google Fonts, but, those fonts are not loaded from Google anymore.

    You can check if Google Fonts are also called from another plugin such as WPBakery Page Builder, Slider Revolution, or others you use.

    See these videos to learn how to disable Google Fonts from WPBakery Page Builder (see video) and Slider Revolution (see video).

    Have a great day!

    P.S: If you want me to check them, I need your WP credentials.

  •  1
    rendjy replied

    Thank you!

  • [deleted] replied

    Happy to hear thatsmile.png

    I will set this ticket as solved from here.

  •   rendjy replied privately
  • [deleted] replied

    Hi rendjy,

    To assist with debugging the issue on your WordPress website, you need to provide the WordPress admin credentials.

    Thanks!