Skip Navigation

[Resolved] Toolset breaks Font Awesome 5 icons in Beaver Builder

This support ticket is created 4 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 2 replies, has 2 voices.

Last updated by Christian Cox 3 years, 11 months ago.

Assisted by: Christian Cox.

Author
Posts
#1537613

I'm using a social media module in Beaver Builder that uses Font Awesome icons. I assume it is Font Awesome 5.

When Toolset is activated, the icons disappear (small boxes display).

I've fixed using this the code from this thread:
https://toolset.com/forums/topic/font-awesome-5-pro-icons-not-loading-correctly-in-beaver-builder/

Snippet:

add_action( 'wp_enqueue_scripts', function() {
wp_deregister_style('font-awesome');
}, -1 );

This appears to work - but is it still necessary? Has there been any fix to this, perhaps a setting I'm missing?
The help thread listed above is just over a year old.

#1537881

Hi, at this time Toolset does not support FA 5, only FA 4. So unfortunately this workaround, or a similar one, is still required. I don't currently have an estimate available for FA 5 support, so I can't say for sure when the workaround will be obsolete.

#1645647

Just a quick update to let you know Font Awesome 5 support has been added, and you can find the settings for FA in Toolset > Settings > General tab.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.