-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Categories Icon in Navigation #121
Comments
Looks like they've removed |
FYI, |
Hey @engram-design ![]() |
Yeah that was it. Thanks @engram-design |
It seems to me that something about the icons is broken. First: Craft uses Font-Awesome-Icons now - It would be nice if CpNav could use the same Icons (f.E. "basketball") Second: When i upload a custom SVG-Icon i do not see anything next to the Nav-Item - But it shows the custom-Icon in the settings. Best regards, |
The state of Craft's icons are still in a bit of disarray, but I agree I'd like to just support Font Awesome in a standard way. I believe we'll be able to make use of their icons but I also don't believe they cover all the native CP Nav icons. The custom icon issue is fixed for the next release. To get this early, run |
Hi Josh - Thank you very much! |
Describe the bug
What happened?
Description
Upstream must have did some refactoring to the CMS icons.
This was 3.7.x:

This is 3.8:

Since updating to Craft CMS 3.8, the Categories icon seems to be doubling up...
In the icon picker for CP Nav, it shows this:
Doesn't seem to affect any functionality. I worked around it by choosing a different icon from the list.
Craft CMS version
3.8.3
Steps to reproduce
Craft CMS version
3.8
Plugin version
3.0.17
Multi-site?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: