There is no way to use the theme Font Awesome lib for other plugins to hook into. When using other plugins that uses icons such as FA icons. Many of them have features such as disable and load theme. But this is not working since PRO FA lib is customized, all classes are changed, those have no any chance to be used by other plugins.
PRO theme doesn’t use the native/default FA lib (CSS file).
Forces us to load x2 FA icons lib .woff and css files.
Bottleneck which should be tackled.
Hi Mike,
Thanks for reaching out.
The icon library is part of the builder core so it can’t be disabled. And it’s very important since it should stick to the version of the library, another version without proper integration could cause icon mismatch, hence, it’s made that way to prevent compatibility issues (it’s made part of the core, unchangeable but could be change by our developer for future changes). And to prevent conflicts with other libraries, we added our own class naming.
I recommend utilising the icons provided by the theme/builder and its class names if you wish to have only one running library. But noted this as a feature request, but please note that having multiple instances of library is not preventable even between plugins (not our theme or plugins) from different developers, hence more conflicts. And having our own built-in naming is just to prevent that.
Thanks!
Thanks but it is not possible to use theme.co’s FA lib in other plugins since they listen to standardised FA icon lib classes.
It is slowing down since I have to load x2. And original FA icon is way lighter than PROs 3 libs don’t know how you managed to make them so big in size.
I dont see why not utilise standardised FA icons which all other page builders do and have never experienced conflicts there. Rather gains due to other plugins can listen to them/page builders FA lib instead of loading x2.
Other plugins to support PRO would require edge cases and change many coded standard fa icons to support pro. They wouldn’t do that once 99.9% use standard FA icon classes. Sorry PRO is the edge case and should follow the standard rather than telling all other plugins to make compatible with PRO which sin’t following FA icons standard lib.
Hi Mike,
Noted, but on a side note, if any plugin requires integration to the theme then it should follow the standard of the system it wishes to integrate. And it should have the ability to adapt between integrations and its own preferred library isolated to the theme.
It is slowing down since I have to load x2. And original FA icon is way lighter than PROs 3 libs don’t know how you managed to make them so big in size.
That means you wish to integrate a different version of the library that is faster as you preferred, that’s going to cause issues since the builder is only integrated with a specific version. And each version has a different set of icon codes and if you loaded a different library that has a different set of icon codes then the builder will fail as it will display different icons, and sometimes no icons at all. That is why in every update, you will see icon issues since the icon codes changed and you’ll have to clear the cache, that’s going to happen too if you force your own icon library to the theme, like the usual FA class (and if another plugin loaded the same FA Classes then the same issue too, conflicts and missing icons). And to prevent all of that, we use our own naming and integrated it in the core, but that kind of integration doesn’t limit anyone to integrate their own libraries.
Font-awesome Pro and 5.0 have many sets of files for the icons different from its predecessor, it’s completely different from the older versions that you thought faster. And it’s not about FA icon standard, remember, they have many different major versions that have different standards from each too, so I’m not sure which standard you’re following. And it’s about Wordpress standard and not FA library standard. Wordpress is modular in which software is developed by multiple people, hence, the priority is always preventing conflicts by using unique names. Even Wordpress loads its own version of jQuery to prevent conflict, and once another plugin forced its own version, the entire feature that depends on jQuery fails too, that is same for icons.
The latest with twice amount of icons and codes
https://fontawesome.com/changelog/latest
The old, faster but fewer icons
https://fontawesome.com/v4.7.0/
Thanks!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.