Font won’t load on shopping pages - by Bas Kling

This topic has 7 replies, 3 voices, and was last updated 2 years, 11 months ago ago by Bas Kling

  • Avatar: Bas_Kling
    Bas Kling
    Participant
    May 14, 2021 at 11:32

    Hi,

    We’ve upgraded to xcore version 3.2.8 yesterday, and since, our font Open Sans won’t show anymore on any of the category pages nor any of the SPP’s. Only the title font, Trajan still shows correctly.
    All static pages display both fonts just fine.

    Can you please have a look?

    -EDIT- : font in footer won’t load either

    6 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    May 14, 2021 at 14:02

    Hello,

    Provide URL and temporary wp-admin access.

    Regards

    Avatar: Bas_Kling
    Bas Kling
    Participant
    May 15, 2021 at 09:26

    Private

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    May 15, 2021 at 14:32

    Hello,

    Update the theme and Core plugin to 7.2.9/3.2.9 versions.
    Connect to your server via FTP and remove wp-content/fonts/open-sans/ folder. After that go to Theme Options > Typography > re-choose font and save settings.

    Regards

    Avatar: Bas_Kling
    Bas Kling
    Participant
    May 16, 2021 at 11:05

    7.2.9 / 3.2.9 doesn’t show in my updates?
    Xstore welcome page says there’s an update available, but my wordpress dashboard or plugins page doesn’t offer the update option

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    May 17, 2021 at 10:59

    Hello,

    I see that the default Dashboard > Updates WordPress menu item on your site. Probably you disabled WP auto-updates using config or one of the third-party plugins did that.

    Regards

    Avatar: Bas_Kling
    Bas Kling
    Participant
    May 17, 2021 at 17:23

    Thanks. Our developer has indeed disabled and set up a staging area.

  • Viewing 7 results - 1 through 7 (of 7 total)

The issue related to '‘Font won’t load on shopping pages’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.