Site logo

[Support request] Switching to local fonts – page and category display errors

Home Forums Support [Support request] Switching to local fonts – page and category display errors

Home Forums Support Switching to local fonts – page and category display errors

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #2404436
    Frank

    Dear GP team,
    I’ve searched the forum and the internet for a solution, to no avail. I use GP Premium latest update. I have embedded local fonts on several websites using GP’s existing approach. One of the sites is https://fynntastisch.de. The fonts are on the server under Upload in their own “fonts” folder and the CSS is correctly integrated under Cutstomer. The normal pages also work fine, all fonts are displayed correctly. But when I select a category in the footer or when I look at another page on the blog pages (the second page for example) the fonts don’t load. The browser console (F12) then shows an incorrect path for the fonts with “page” or “category” in the URL. You can see it well in the console. It’s probably just a small thing, but I can’t find the fault. What can I do?
    A thousand thanks in advance. (and sorry for my bad english).
    Frank

    #2404439
    Frank

    Oops, sorry, here is the correct address for the website in question: https://fynntastisch.de

    #2404682
    David
    Staff
    Customer Support

    Hi there,

    in your @font-face CSS set the URL to an absolute path eg. https://fynntastisch.de/wp-content/uploads/fonts/alegreya-sans-v21-latin-300.woff2

    #2404790
    Frank

    Hi David,
    thanks for the quick reply and help. I replaced all URLs with the absolute path in the Cutsomizer CSS, looks great now. I don’t see any font errors anymore and I think that was the problem. I’ve been looking for so long, soon I’ll ask you sooner. 😉 Thanks.
    Frank

    #2404798
    David
    Staff
    Customer Support

    Glad to be of help ! And don’t be afraid to ask 🙂

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