Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
I cant seem to get the icon configuration right for font awesome. Here is the directory structure
And the config I am using with the error is as follows
So the question I have is what needs to be in the css path, and what needs to be in the rules source file; the documentation does not match the code from GitHub.
i am still having challenges with this as well... perhaps a simple tutorial for those of us having trouble closing the gap.
also, any help with icon display when using leblender? @item.GetValue("icon") returns some json... not sure what to do with that?
I don't know Iconic but fontawesome went from using just fa- plus the iconname to far-, fas-, fal-, etc.
Could that be the problem?
No, but I think you are right, if I don't used the minified css, I get an error about the regex being incorrect -- unfortunately, there are no styles in the css file, so I am not really sure quite how to configure this up to get it working... any guidance would be appreciated
Can you for testing purposes include fontawesome 4?
This was asked on the Slack group; I showed a solution as I needed it myself as well.
This is the result I ended up with:
And this is the configuration needed in Iconic:
With each CSS file (e.g. /css/font-awesome/fa-brands.css) only containing the rules appropriate to that selector, for example:
It was a little bit of legwork creating those individual CSS files, but REGEX find/replace sped things up so only took a few minutes in reality.
I created mine using FontAwesome Free (v5.3.1) and happy to share the CSS files to save you creating them yourself.
That would be AWESOME! you can message me in slack to coordinate... cant tell you how much I appreciate that!
Here you go https://www.edg3.co.uk/blog/how-to-add-font-awesome-v5-icons-using-iconic-in-umbraco/
Just added a request to the pro version repo to get a version that is implemented similar to the 4 series.
I wonder if you would share your process for creating the files you created so I can apply that to the pro version?
Apologies, only just seen your reply.
I actually found another way on second look. On the Cheatsheet if you view the source there is a JSON object containing every icon - including attributes to say whether they're free/pro and what group (brands/regular/solid) they belong to.
Parsing the JSON is simple (much simpler than the original hacky method REGEX find/replace)!
Have pushed up to a Github repository for ease (and will update the blog post to reflect this):
I'm sure there's an even better way of generating these using the API, but I haven't looked into that.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted