Forum

The forum is a free service supported by community members. Please consider opening a support ticket if you need timely help.

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 24 Sep 2020 01:55 PM by  Steve L
view errors with sf 16.9
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages


Basic Member


Posts:281
Basic Member


--
17 Sep 2020 11:04 AM

    Hi Stephen.

    I have upgraded to version sf 16.9
    The display is not good now.
    The rating stars, minicart icon, expand signs of the category are all squares now.
    Refresching and ctrl shift R does not resolve this.
    Do you have a suggestion to correct this?

    With regards, Ton

    Attachments
    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    17 Sep 2020 02:44 PM

    Hi Ton,

    Your skin has a file /Portals/_default/Skins/Galore/common/css/base.css is specifying the incorrect font family that is overriding the default Font Awesome library:

    .fa {
      font-family: FontAwesome;
    }

    Please remove this and try hard refreshing your browser (CTRL + SHIFT + R).

    0


    Basic Member


    Posts:281
    Basic Member


    --
    24 Sep 2020 11:09 AM

    Hi Stephen,

    Your solution works.

    The host of my website has put the following css into the portal settings wich is working also.
    .fa, .far, .fas {
        font-family: "Font Awesome 5 Free";
    }

    The support of Easydnnsolution skin says:
    -------------------

    Hi Ton,

    Our theme uses Font Awesome 5 and the module uses Font Awesome 4 so there is a problem. You can do by the instructions.

    Best regards,
    Damir Kapustic

    ------------------------

    Are you moving later also to version 5 ?

    With regards, Ton

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    24 Sep 2020 01:55 PM

    The Storefront 16.9 is already compatible with both Font Awesome 4 and 5, which means in technical terms we include both "fa" and "fas" in the class attributes so that either version will render. However, your skin was actually specifying the wrong font family (it specified the font family for Font Awesome 4) even though it included the Font Awesome 5 library. 

    In any case, I'm glad the change you made worked. In the future release we will drop support for the old Font Awesome 4 (and keep to Font Awesome 5 only) once sufficient users have migrated to Font Awesome 5 so this issue should not happen again.

    Thanks!

    0
    You are not authorized to post a reply.