incorrect path to local google fonts after migration

  • Resolved antonie2008

    (@antonie2008)


    1 year, 3 months ago

    Hello,

    after migrating the site, the local Google fonts were*** only displayed correctly in the backend, but not in the frontend.

    ***To make the fonts work, I manually added the call to the local Google fonts to the CSS file -> this double font call is of course only a temporary measure until the actual problem is solved.

    The source code of the page shows that the path to the development domain could not be correctly replaced during migration. Instead of “www.[entwicklungsdomain.de]/wp-content/fonts…” it is now “/www/htdocs/[ftp-User]/[entwicklungsdomain]/wp-content//fonts”. The name of the development domain is still included AND there is a DOUBLE slash to the “fonts” folder…

    Unfortunately, I can’t find the string with the Search+Replace plugin, so I can’t replace it either, so I assume it’s generated dynamically… So my question is: How does NEVE create the call to the local Google fonts? How can I edit the path afterwards?
    And if it’s a problem I need to solve in the database, I need a “for dummies” guide, please.

    Thank you very much for your help.

    Antonie

    • This topic was modified 1 year, 3 months ago by antonie2008.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi @antonie2008,

    Thanks for choosing Neve!

    You could try to reload the fonts as explained here, or to load them as custom fonts by following the steps provided here.

    Have a nice day!

    Thread Starter antonie2008

    (@antonie2008)

    Hello Lucia,
    Thank you very much for your answer. As mentioned, I had already managed to add the font call for the local fonts manually. My problem was that I wanted to replace/repair the wrong font call links in the header, but didn’t find them…
    In the meantime I did the migrated again and was able to resolve the problem.
    Interestingly, even with the Duplicator plugin I used now, the path to the fonts was initially wrong (as was the case with another tool that I used for the first migration) – and after I had deleted ALL the data in the path of the target domain and replaced the database completely and then restarting the import, the font call was finally correct.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘incorrect path to local google fonts after migration’ is closed to new replies.

Tags