Conflict with official FontAwesome WordPress plugin

  • beCreative Media

    (@becreativemedia)


    1 month, 3 weeks ago

    The ACF: Font Awesome Field Plugin works perfectly fine on its own. However, when the official Font Awesome WP Plugin (https://wordpress.org/plugins/font-awesome/) is additionally used to enable the use of icons within paragraphs, a conflict arises that causes the icons in the ACF: Font Awesome Field to no longer be displayed.

    WordPress and all plugins are up to date. Unfortunately, the filter ACFFA_admin_enqueue_fa did not provide a solution.

    Is there a way to fix this or make it work through filters?

    Thank you and best regards.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Matt Keys

    (@mattkeys)

    1 month ago

    Hello @becreativemedia,

    Sorry for the late reply I was out on vacation and am just catching up. These two plugins used to work together, but I do see the problem you are experiencing.

    Or at least I did briefly. Switching my kit settings from “SVG” icons to “Web Fonts” fixed the issue. But then going back to SVG the issue came back again.

    However by going into the official FontAwesome plugin settings and clicking “Refresh kits data” while having the kit configured to use SVG icons, everything seems to work happily together again.

    Let me know if that fixes it for you too.

    Matt

    • This reply was modified 1 month ago by Matt Keys.
    Thread Starter beCreative Media

    (@becreativemedia)

    3 days, 1 hour ago

    Hello Matt,

    No worries at all — I hope you had a great and refreshing vacation!
    Thanks so much for the detailed explanation. I gave it a try, and unfortunately, I’m still seeing the same issue.

    Let me know if there’s anything else I could try or if you need any more information from my side.

    Plugin Author Matt Keys

    (@mattkeys)

    1 day, 10 hours ago

    Shoot, you are right it still isn’t working with SVG icons. It was for me for a moment but I think I checked too quickly after switching from WebFonts to SVG and the kit just hadn’t updated yet.

    Can you confirm you are using SVG icons too? I wonder if this is something we might need FontAwesome to look at.

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