Sorry, one last v basic question.No, you should only add missing icons to the appropriate list
Yes, icons that are not being display (altouhh they should be there), eg. that are visually "missing"When you say "missing icons" do you mean icons that are just not displaying?
Yes, most likely - if you don't see any "missing" icons, the renderedAnd if that is the case, if I am see all the icons I have added (outside of stock xenforo) then the addon is configured as it needs to be and working
fa.css
does only include a handful icons and you only see network requests for the -min.woff2
files everything should be working fine.Thanks, not sure how I missed those posts referencing duotone icons.
Bugs Fixed
- Duotone icons were not usable if style option Load subsets only was enabled
This bugfix significantly increases the subset size (by a factor of two) for the duotone font which could lead to reaching the transfonter.org limit of 5000 characters a lot easier.
To mitigate this, duotone has been splitted into its own subset chunk, so this change will slow down rebuild time a little bit.
Future versions will check if there are any styles that...
No, you don't need to make any changes (you don't even need to update if you didn't hit any of the fixed bugs).just a question. if everything was running fine and well on the previous version. i don't really need to make any changes after updating to this right?
Duotone icons /whie are not being used at all by default XenForo style) are a font icon style that uses two codepoints for one icon, allowing two-colored icons.i don't even know what duotone fonts are and if they are even used in xenforo default theme. thanks!
If the option Load subsets only is disabled, the CSS for all icons is available and will reference the original font files in case an icon is missing in the subset(s).Does not know If this correct but I am recommended settings Load subsets only = NO because we have lot of icons are missing issue and all are fixed with disabling Load subsets only option.
In thise case the icons most likely were not added to the correct list. Re-cehck which icons exactly are missing, add the to the list and verify that they are incluced in the subset(s).Also added missing icon in this list but does not fix to showing.
If you do not know exactly which icons are missing, I'd recommend to temporarily enable option Automatically add missing icons.
i:before {
content: "\f6b7";
:before {
font-family:'Font Awesome 5 Pro';
content: "\f505";
:before { .m-faContent("\f2f6");
<i class="far fa-user-edit"></i>
It shouldThen Enabled option Load subsets only with Enabled Automatically add missing Icons option but this does not add any missing Icons.
No.Do we need re-run Rebuild Font Awesome subsets after enabled option Automatically add missing icons?
As stated before, it doesn't matter if icons are listed multiple times ore not; they will only be use once anyway.What about if we add Manually duplicate icon in list then that does check and remove duplicate icon entry from this list?
I don't use Safari (as I do not have apple hardware), but there relly shouldn't bee much difference.I have a bunch of missing icons but they show fine in Safari. They’re missing in Firefox and the other browsers. Do you know what Safari does differently than the rest? Is this something that should be accounted for in the add-on itself?
All of those should work just fine and be found automatically; you can check this by running a rebuild with log level set to Debug.A few of my custom icons aren’t missing but most of them are. I think this is because of my messy CSS and how I have added icons over the years with inconsistent formatting.
Can you tell me which of those the add-on prefers? Maybe even which one XF prefers? Or any other tips/explanations about the different ways of adding icons.
I did't get any further feedback on this - do you still experience this error with 1.2.0 RC2/RC3?hmm well I updated and the error still happened
We use essential cookies to make this site work, and optional cookies to enhance your experience.