Host fonts locally in “NS Cloner”-copied multisite

  • Resolved nilskamm

    (@nilskamm)


    5 months ago

    Hey everyone!
    I copied a multisite with the plugin “NS Cloner” and everything seems to be good, except one thing.

    In the source site we activated “Local fonts hosting” and it works well. In the copied site the fonts selected and the setting for local hosting are the same but it doesn′t work. The fonts in the frontend are not the selected fonts.

    I already tried deactivating and reactivating the setting or changing it in the functions.php with the code snippet as written in the theme docs (https://docs.themeisle.com/article/1919-how-to-host-hestia-fonts-locally) but no luck.

    In the preview of the Customizer the fonts work, but not on the site itself.

    Any idea what i can try to solve that?

    Thanks a lot!
    Nils

Viewing 5 replies - 1 through 5 (of 5 total)
  • rodicaelena

    (@rodicaelena)

    Hi,

    Make sure this is not related to caching.

    1. Clear the cache in your browser.
    2. If you have access to your hosting control panel, look for any caching features provided by your host and clear them.
    3. Check if there are any additional caching services like Cloudflare that might be caching the mobile version of your site and clear those caches as well.
    4. As a last resort, you might want to consider temporarily disabling all plugins except for the theme’s essential plugins and see if the issue persists. This will help determine if a plugin conflict is causing the problem. For this, you can use the Troubleshoot mode of the?https://www.ads-software.com/plugins/health-check/?plugin.

    Kind regards,

    Rodica

    Thread Starter nilskamm

    (@nilskamm)

    Hey @rodicaelena !

    Thank you for your answer!

    It is not related to caching and i think the Troubleshoot mode of the health-check plugin doesn′t work with multisites. I downloaded the plugin, activated the Troubleshoot mode, but plugins were still active.

    Anyway. I found what′s wrong but i don′t know how to fix it properly.

    The theme tries to load the fonts from a wrong place. As example i use the font Kelly Slab.
    The site where it works and which i used to clone the new one, loads the file from https://www.domain1.com/wp-content/uploads/sites/10/fonts/kelly-slab/-W_7XJX0Rz3cxUnJC5t6fkQLfg.woff2

    The cloned site tries to load it from https://www.domain2.com/www/htdocs/v009923/wordpress/wp-content/uploads/sites/10/fonts/kelly-slab/-W_7XJX0Rz3cxUnJC5t6fkQLfg.woff2 what is just wrong and not accessible.

    I then checked what is happening, when i disable “Local fonts hosting” in the working site and then clone a new one. After cloning the new site i activated “Local fonts hosting” again, but it doesn′t work and also tries to load the font from an inaccessible place: https://www.domain3.com/www/htdocs/v009923/wordpress/wp-content/uploads/sites/10/fonts/kelly-slab/-W_7XJX0Rz3cxUnJC5t6fkQLfg.woff2

    Then i searched for “/www/htdocs/v009923/wordpress/wp-content/uploads/sites/10/fonts/kelly-slab/-W_7XJX0Rz3cxUnJC5t6fkQLfg.woff2” in the database and it exists only one time in the table *_sitemeta, meta_id 1255 with the site id 1.

    Because it only exists one time but i have 3 sites using the same setting, i do not want to change it without really knowing what i′m doing.

    How can i change the path to the local fonts seperatly for every site of my multisite network or what is the right way to let all sites use the same local font files?

    Thanks a lot!

    Hi,

    I understand. Thank you for the update.

    Unfortunately it’s hard to help without access to your site. This seams to be a bit more complex.

    I would suggest for this if possible maybe hiring a developer to help.

    Kind regards!

    Thread Starter nilskamm

    (@nilskamm)

    I decided to just not clone the site with NS Cloner. If i create a new site everything works.

    Hi,

    Great! Thank you for the update.

    Kind regards,

    Rodica

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.