Replies: 1 comment 1 reply
-
That's correct. I was not aware that FontAwesome 6 was such a breaking change, which is why I slipped it in a patch release. I've added a note retroactively to the changelog. If you set up configuration validation as described in the creating your site guide, it will at least tell you which icons are no longer valid in If somebody manages to provide a script to automatically rename all icons in Markdown files, feel free to share it here. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is a sort of PSA (I assume).
With Fontawesome v6 came a lot of icon renames. Depending on where or for what you used the icons would this have minor inconveniences (i.e.
:fontawesome-<type>-<icon>:
not rendering) to complete breaking of your deployment/build process (Update: I no longer use netlify for my personal pages, so this link won't work anymore).This affects anyone that uses the latest Material for MkDocs release (I think. Or is it related to the emoji extension?) and the best way to fix this is by renaming any appearance of old icon names in the
mkdocs.yml
, any Theme extensions you have and the markdown files themself.Fontawesome provides an entire list of all changed icon names in v6:
https://fontawesome.com/docs/web/setup/upgrade/whats-changed#icons-renamed-in-version-6
Just to be safe is here the obligatory message that this is not an official message from Fontawesome. I do not work for them nor claim to do.
Any info is provided as is without guarantee, bla bla bla, you know the drill...
Beta Was this translation helpful? Give feedback.
All reactions