Closed superbilk closed 9 years ago
As everyone might have expected, it's not a bug with font-awesome-rails. It's some other gem (still don't know wich broke everything). Sorry.
Just FYI. Bootswatch-rails packages a competing and outdated version of FontAwesome.
Not sure if that was your problem, but maybe worth investigating.
On Saturday, August 22, 2015, Chris notifications@github.com wrote:
As everyone might have expected, it's not a bug with font-awesome-rails. It's some other gem (still don't know wich broke everything). Sorry.
— Reply to this email directly or view it on GitHub https://github.com/bokmann/font-awesome-rails/issues/149#issuecomment-133769097 .
Thanks. In my case ist was sass. It's working with 3.4.15 and 3.4.16 but not with 3.4.17 So I set the version to 3.4.16 and will wait.
Unfortunately I don't know enough about sass (or font-awesome) to see whats the problem here. https://github.com/sass/sass/blob/stable/doc-src/SASS_CHANGELOG.md
Hey @superbilk - thanks for this, don't be sorry - saved me a lot of time. Having the same issue - after upgrading FontAwesome and some other gems, it stopped working in production. The problem is indeed with sass - I am also locking it now at 3.4.16 and its working (was 3.4.17, broken).
Is this a FontAwesome issue or sass?
I think this ticket should be kept open until it is resolved, even if the solution needs to be done elsewhere - other people searching for it might not search in the "closed" tickets group.
Thanks for opening an issue on sass, @DannyBen I'll reopen this and edit my first comment accordingly.
The friends at sass just released 3.4.18 which fixes this.
:+1: Thanks everyone for working through this with the Sass team and keeping us in the loop here.
@superbilk Please close this issue out once you're satisfied with the Sass fix.
it's also fixed for me :-D thanks to the people at sass and @DannyBen
Cool
tl;dr sass 3.4.17 breaks font-awesome-rails, pin your version to 3.4.16 and you are fine.
Hi erveyone,
I'm working on this, since I upgraded from font-awesome-rails 4.3.0 to 4.4.0 earlier that day. (see more at the end)
In production with precompiled assets (through capistrano) I only get empty boxes instead of icons. I have the issue in production right now (https://www.happinessmetric.com -> you should see some icons in the navbar)
If I precompile my assets on my local machine (
RAILS_ENV=production bin/rake assets:precompile
) I can reproduce the problem (all caches cleared). No matter if I startrails s
in development or production mode. And I also tried different settings onconfig.assets.digest
andconfig.assets.compile
.If I use the pipeline in development, everything is fine. That's my only working 'solution' at the moment.
Precompiled I get the correct filenames
and these are referenced correctly in my application.css. There are no 404 or any other errors.
I would guess precompiling somehow breaks the font-files. But I have no idea how to further investigate... I've also put these files online, maybe someone knows how to check these: https://www.dropbox.com/sh/a7x8o5raietzbz8/AACg_slTHfsJmNFZleJdNMW9a?dl=0
What I also did (referencing your debugging guidelines)
<i class="fa fa-facebook-square fa-2x">
)As I said, I upgraded font-awesome-rails. And there are some other gems updated. Maybe this also helps:
Cheers,