- This topic has 3 replies, 2 voices, and was last updated 3 years, 2 months ago by Leo.
February 25, 2018 at 11:25 am #505333Al
I put up a previous thread on this and temporarily solved it by turning off GP Premium. I have taken some further time to look at this problem since I found my temporary solution turned off GP Font Awesome icons in my topbar which I didn’t notice right away and the client was reviewing the site.
I have the Photo Gallery and Toolset plugins installed which are needed for this site. The problem was that icons in their user interfaces break when GP Premium was on ie. the icons for “full-screen” and “arrows” to move the gallery slider went missing and were replaced with broken image icons.
I have isolated the problem to the GP Hooks module that contains the Font Awesome code in the WP Header.
<script defer src=”https://use.fontawesome.com/releases/v5.0.6/js/all.js”></script>
<link href=”https://use.fontawesome.com/releases/v5.0.6/css/all.css” rel=”stylesheet”>
These plugins separately in the page header call Font Awesome CSS sheets but version 4.
<link rel=’stylesheet’ id=’font-awesome-css’ href=’https://xxx.com/wp-content/plugins/types/vendor/toolset/toolset-common/res/lib/font-awesome/css/font-awesome.min.css?ver=4.7.0′ type=’text/css’ media=’screen’ />
<link rel=’stylesheet’ id=’bwg_font-awesome-css’ href=’https://xxx.com/wp-content/plugins/photo-gallery/css/font-awesome/font-awesome.css?ver=4.6.3′ type=’text/css’ media=’all’ />
There must be some sort of conflict here.
I have come up with another temporary solution by calling Font Awesome 4 version icons in my topbar rather than version 5 ie. using fa-fa rather than fas-fa.
I have set up a staging site so I can show you this problem without my temporary solution. I have activated the GP Hooks module which knocks out these other icons. The URL below shows you a gallery with this problem.
It may not be your theme’s fault but if you have any suggestions, I would love to hear them.February 25, 2018 at 6:34 pm #505565LeoStaffCustomer Support
We are in the process of upgrading to FontAwesome 5 – FA hasn’t made it easy for us 🙂
I would think that the problem will be fixed once we upgrade to FA 5 on our end as well.
For now your workaround of changing the prefix should be the best way.
Thanks for your patience!February 26, 2018 at 8:39 am #506062Al
Understood. Thanks.February 26, 2018 at 10:06 am #506131
- You must be logged in to reply to this topic.