Beaver Builder enqueuing 2nd instance of Font Awesome

Hi guys, in my theme I have this:

add_action( 'wp_enqueue_scripts', 'click_enqueue_assets' );
function click_enqueue_assets() {
    wp_register_style(
    	'font-awesome', 
    	get_stylesheet_directory_uri() . '/lib/css/font-awesome.min.css',
    	false,
    	'4.2.0'
    );
	if ( !is_admin() ) { 
		wp_enqueue_style( 'font-awesome' );
	}

}

The Font Awesome stylesheet is registered with the handle font-awesome, same like in the plugin. However the plugin is still including a 2nd instance of font awesome from wp-content/plugins/bb-plugin/css/font-awesome.min.css

See the problem here:
https://clickwp.com
http://dev.clickwp.com (staging site without the CDN)

Shouldn’t the plugin not enqueue the Font Awesome stylesheet a 2nd time after my theme already registers it? If not, how can I prevent Beaver Builder from doing so?

Thanks (Merry Christmas & Happy New Year in advance)!

Have you tried this free plugin?
https://wordpress.org/plugins/dequeue-font-awesome/

Hmm… looks like I was mistaken. WordPress is loading Font Awesome from Beaver Builder rather than from my theme. I’d prefer to load it from my theme - is that possible?

Hi David! Merry Christmas and Happy New Year to you as well!

If WordPress is giving preference to our version of FA versus the version in your theme, you could probably dequeue our version of FA first, then enqueue yours. I am not 100% sure if that will work, but I would experiment around with that. Please let me know if that works for you. If not, we can explore other options. Since I just pulled it up, here’s a quick link to the codex on wp_dequeue_script:

http://codex.wordpress.org/Function_Reference/wp_dequeue_script