I just checked the Font Awesome version, which was used in the panel (Kirby 2.1) and it was 4.2.0
But the actual version of Font Awesome is 4.4.0 - so we’re missing a lot of icons (I needed the
.fa-diamond icon, which is not included in 4.2.0).
So I updated the Font Awesome version myself (simply with a
@import in my customized panel.css).
Will Kirby 2.2.0 include the newest version of Font Awesome?
(diamonds in the sky… well, at least in the upper-right corner)
I just updated the 2.2 beta to fontawesome 4.4
I already thought so, but I did not want to develop with the nightly bèta - so I’m “stuck” with 2.1.0, but can enjoy all my new icons right now (and I’ll wait patiently for the final release of 2.2.0).
Keep up the good work, amazing!
Thank you very much!
In Kirby 2.2.3 the two font files are updated to 4.5.0 but the css file
\panel\assets\css\panel.min.css looks like:
* Font Awesome 4.5.0 by @davegandy - http://fontawesome.io - @fontawesome
* License - http://fontawesome.io/license (Font: SIL OFL 1.1,
CSS: MIT License)
I do not know whether the addition “?v=4.4.0” at a local installation of the font files is required.
That query string is there because of cache busting I guess. Would you mind opening an issue at the Panel repo?
Since I have no account on github: Please feel free to create an issue. Thanks.
But that can’t be automatically inserted. The variable definition follows afterwards.
You may want to delete only the version number there (and add it after the variable definition, if you want)…
That comment block needs to stay intact because of the license. We will have to change it on each new FontAwesome version, but that’s fine.
That’s a big difference. One thing is leaving the license intact, in case other people come across the code.
The other thing is attribution, i.e. officially acknowledging the author on the website.