[Steven Zahm]

@ dominic

Looks like both Avada devs and I made the same mistake. Neither I or they prefixed their font family names for our custom font icon sets (nothing to do with Font Awesome). We both used icomoon to create the custom icon font so both have the icomoon font-family declared but they both contain different glyphs, so, which ever loads last is being used. In this case, It seems the Connections version is being loaded last.

I can push out an update later this week which properly prefixes the Connections icon font family name. The Avada devs should be encouraged to do the same, if you want to open a support ticket with them.

Apologies for the trouble!