This thread is resolved. Here is a description of the problem and solution.
Problem:
Toolset uses an older version of Font Awesome (4.7) but the current version is 5.
Solution:
We already have an internal ticket about upgrading the version we use, which should happen soon.
0% of people find this useful.
This support ticket is created 6 years, 5 months 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.
We are using Toolset on a website that is already using Font Awesome 5, however Toolset Types/Views is insisting on loading Font Awesome 4.7.0 on any page that contains a view on it.
Types currently has a way of disabling Bootstrap CSS, but it doesn't appear to have a way of disabling Toolset's Font Awesome.
It is very common for other plugins and themes to load font awesome as well, and a lot of them are already using Font Awesome 5.
Given that toolset is only using Font Awesome 4.7, it would be ideal if Toolset offered a way of disabling it's own Font Awesome output in order to allow other themes and plugins to load font awesome 5.
I've seen a few PHP code snippets on your forums for disabling Font Awesome CSS in Toolset, however none of those appear to work any more.
I was just looking at this to see how we might dequeue this stylesheet, but on my local test site I don't see it added anywhere.
You said it is added to any page that contains a View, but I have a page with a custom search View inserted, and on the front-end looking in the browser dev console there is no Font Awesome stylesheet added.
Can you clarify the specific circumstances where you see it added?
I am using the updated plugins versions, Types 3.0, Views 2.6 etc.
We weren't able to get it working, so we ended up reverting back to Font Awesome 4.7.x for this project.
Does Toolset have plans to upgrade from FA 4.7 to FA5? I'm sure a lot of your users could benefit from using FA5, and as more and more other plugins start using FA5 it is likely to cause support issues whilst Toolset only has FA 4.7.
I checked and we already have an internal ticket to update to Font Awesome 5, I added a message to it with your vote, it should happen before too long.
Still no option to prevent Font Awesome loading. Is there a way to disable Font Awesome loading by Toolset thru function.php, as font is loaded by theme already?
