Fontawesome Pro Free Download

0 views

Skip to first unread message

Amelie Robertos

unread,

Aug 3, 2024, 3:45:37 PM8/3/24

to nnehretela

You enter assets directory and then follow NPM instructions. That is it. Phoenix assets pipeline is exactly the same way as any other webpack project with specific build directory (../priv/static) and that is all.

I did integrate FontAwesome in my project very differently.
It seems that Phoenix(1.5.0) already shipped with webpack along with a bunch of loaders like node-sass, css-loader, etc.
I downloaded the fontawesome zip as a whole and dumped the scss and webfonts folders in my /assets/css directory so it looks like this

Next, I had to go to my app.scss and load fontAwesome.
I also had to specify the $fa-font-path before doing the imports above since I am using a customized directory structure and FontAwesome needs to load webfonts to make it work:

Next, Webpack complained it was missing a couple of loaders that help with loading fonts?
so I had to install them like this:
npm install --save-dev url-loader
npm install --save-dev file-loader

Hi Pkollitsch and thanks for the answer. However I only have a local site in which I want to test out fontawesome. What I want to know is what files to download, the locations to store them and basic usage, i.e how to use them (reference them) in my template, for example list.html and single.html. I have an idea regarding using icons for my taxonomies (categories and tags). I saw some examples from Hugo Bootstrap4 theme and Love It theme. So I just mean simple basic step-by-step instructions.

I just tried it on a live instance of Discourse and I am getting the same results as you are. It works in my local development environment, and it works here on meta.discourse. If I include the link to one of the SVG images from this topic on my own forum then it displays correctly. I am guessing that SVG file uploads are being disallowed for security reasons.

Drag and drop a multiple selection from your file manager into the input box at yoursite/admin/customize/emojis and you will see them added to the Custom Emoji list, with a default name that is the same as the filename.

Get the fontawesome SVGs here: GitHub - Rush/Font-Awesome-SVG-PNG: Font Awesome split to individual SVG and PNG files of different sizes along with Node.JS based generator (link from a previous post in this thread)

More likely a caching related because if you append something like ?nocache=1 on the URL, you would not see the fontawesome-webfont-ttf-v-4-7-0 error 404. And X and PRO is now using FontAwesome PRO 5 (not 4.7.0).

We have an HTML site that we converted to another CMS years ago. Our client wants to move to the latest version of that particular CMS, the problem is that the new version does not support many of the add-ons that we had acquired over the years - so now a dead horse and they are treading water for the time being.

It also sounds like ContentBlocks might be a good fit for you. Not specifically for your icons (although those solutions can be integrated there as well) but in general to give your client layout and content templates to work with.

Thanks for the detailed info. Just tried to install FontawesomeForMODX and got this error:
Could not download and create transport package with signature: fontawesomeformodx-

No issues with any other packages. All google searches suggest mysql is possiblt segfaulting or running out of ram. Nothing wrong with mysql as every other package installed. Could it be a result of Fred being install with FA for Fred???

I have a vexing problem, and I am sorry I cannot easily provide a reprex of the issue. I have created a quarto website for my course. In that project I have created a table with some columns that have fontawesome icons that will link to either pages within the website or external links. Basically, something like this

But it will not render with the fontawesome icons. It worked with Rmarkdown in years past. Also, it seems I was able to render it at one time, but that behavior stopped. So I do think something is wrong with the code necessarily, but with how my project is set up in some way (organized, defaults, something).

R Markdown and Quarto works a bit differently, especially regarding tables. gt will output some HTML and Quarto will parse this HTML. If you have some Markdown content to be processed you have two solutions

This does not insert the JS library into the resulting HTML. It just load the fontawesome R library. But you are not using any of the fontawesome function that insert in the doc, so at the end you have no JS lib in the HTML

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.

I can change the content: "v"; and it appears in text so I'm guessing the font-awesome isn't loading or something it blocking it. I tried to apply the code to the domain header under HubSpot settings but nothing's working. Anyone have a fix?

Thanks so much! I tested this out and i removed the Kit from the account header settings and replaced all the and @import to the link above and still seems to be appearing as squares (bolder squares, haha)

The problem with that is that your kit is not properly setup in the fontawesome site or this link has expired or the license has expired, difficult to know right now, but it is because of this that it probably doesn't work, you should check your console to see that the request to the kit is not authorized:

So to sup up, you should first get rid of this kit, and then use the code you posted to make some tests, if the issue remains, just post here with some more details so we can look into this, but this kit is most likely the issue. You're probably even trying to load differrent versions of fontawesome as kits are not part of the 4.x.x version as far as I know.

Note: Hubspot already supports and loads fontawesome, take a look in this post. There are also steps inside this post for loading other versions of fontawesome with kits, maybe you want to get rid of the code you posted here and go on with a kit instead, whatever the case you want only one implementations whether its kits or self hosted. Just make sure you don't get the error.

Thanks, I will look further into the post you supplied but the way this theme was built I would have to start this header module from scratch and would prefer fixing this problem in case the fontawesome css affects other modules

How you install our vue-fontawesome component will be different depending onwhether you are using Vue 2 or Vue 3. Make sure to only install theappropriate one that matches the version of Vue you are using.