• Resolved Antony Booker

    (@antonynz)


    Thanks for this plugin. I noticed on some devices there is a conflict with Font Awesome 5 Brands if it’s used elsewhere on a site. This is due to the browser trying to download the Font Awesome 5 Brands font files in the /styles/fonts directory in this plugin but they are missing.

    Would it be possible to remove the bands code below in the fontawesome-all and fontawesome-all.min files to prevent other font awesome calls trying to download those files?

    @font-face {
    font-family: 'Font Awesome 5 Brands';
    font-style: normal;
    font-weight: 400;
    font-display: block;
    src: url("fonts/fa-brands-400.eot");
    src: url("fonts/fa-brands-400.eot?#iefix") format("embedded-opentype"), url("fonts/fa-brands-400.woff2") format("woff2"), url("fonts/fa-brands-400.woff") format("woff"), url("fonts/fa-brands-400.ttf") format("truetype"), url("fonts/fa-brands-400.svg#fontawesome") format("svg"); }

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author annastaa

    (@annastaa)

    Hello Antony,

    Thank you for your interest in our filtering plugin!

    Indeed, we include a “lightened” Font Awesome version with the filters, but if you have another plugin (or theme) serving the full Font Awesome 5 Free package, you have the option of disabling the filters’ FA support altogether. To do that, please go to the annasta Filters > Style Settings tab of your WP admin and set the Font Awesome support option to “Disabled“.

    If that doesn’t work, please feel free to let us know so that we could look for another solution!

    Thread Starter Antony Booker

    (@antonynz)

    Thanks for the quick reply. Having the disable option is great but would it be possible to remove the brands font family reference from the FA stylesheets in the plugin as font awesome is often used on the sites.

    As the plugin doesn’t include the brand font files but declares the font family some browsers may try to download the brand fonts from this plugin but the files will be missing.

    Plugin Author annastaa

    (@annastaa)

    Hello again Antony,

    You are absolutely right, we have already looked further into this and have committed the fix to the next version. Thank you so much for bringing our attention to this inconsistency!

    Plugin Author annastaa

    (@annastaa)

    Hello Antony,

    The newly released version 1.7.8 includes the fix for the issue discussed in this thread, so I will mark this as resolved. Please don’t hesitate to let us know if there is anything else that has escaped our attention. Thank you for helping make the plugin better!

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