• Resolved oldmankit

    (@oldmankit)


    Atomic blocks is using an outdated version of font-awesome. When I try to get the updated version using the official font-awesome plugin (which by default loads fonts from a CDN), I am unable to. Atomic block’s definitions are getting priority and so I can’t use any of the new icons.

    The official fontawesome plugin even tries to deregister other plugin’s versions of font-awesome, but in this case it fails and Atomic blocks seems to over-ride everything. Here is the relevant part of their documentation:

    “Unregistered clients” include any themes or plugins that attempt to load their own versions of Font Awesome using the normal means of loading JavaScripts or stylesheets in WordPress.

    If this plugin detects them, it will display them on the admin settings page. Checking the box to “Remove unregistered clients” just blocks their attempt to load a conflicting version of Font Awesome but does not otherwise interfere with their functioning. Most of the time, the version you want to load will work just fine for them. So this option is intended to both allow those unregistered clients to continue working as intended, while stopping them from breaking the rest of your icons.

    But, your mileage may vary. Since those clients haven’t registered their requirements with this plugin, we can’t be sure what they really require in order to work as intended. You could enable this option and then view the outputs of those clients. If they seem to look as expected, great. If not, try enabling the v4shims in case the unregistered client expects to be able to use version 4 icon names.

    Our hope is that other themes and plugins will use this framework to register their Font Awesome requirements, to ensure that icons are working across all of your posts and pages, including content from those themes or plugins.

    A short-term fix would just be for AB to get the latest version of the icon fonts and release that in the next update.

    For now I have to choose between using AB and using the latest version of fontawesome, which is really no choice, I have to keep using AB. But it would be super if I could use both.

    • This topic was modified 5 years, 7 months ago by oldmankit.
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Unable to upgrade font-awesome version’ is closed to new replies.