Skip to content
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

v3 fontawesome icons: Failed to load resource: the server responded with a status of 404 (Not Found) #316

Open
javierburongarcia opened this issue Aug 14, 2013 · 10 comments

Comments

@javierburongarcia
Copy link

Font assets (fontawesome) are compiled but sass doesn't create the right path to them:

instead of ´assets/fontawesome-webfont-45d370640ec2f9d098a7a7d19bf3be1a.woff´ the css file is showing 'assets/fontawesome-webfont.woff´

@holman
Copy link
Member

holman commented Aug 15, 2013

Strange- I haven't seen this at all.

@maddox
Copy link
Member

maddox commented Aug 15, 2013

I have this on my local install. I didn't do any investigating though. I just have squares everywhere.

On Aug 15, 2013, at 10:10 AM, Zach Holman notifications@github.com wrote:

Strange- I haven't seen this at all.


Reply to this email directly or view it on GitHub.

@javierburongarcia
Copy link
Author

with ´env: development´ assets are not fingerprinted so icons show correctly. did some research but can't locate the error

@johnduhart
Copy link

I'm also experiencing this outside of the development environment.

@holman
Copy link
Member

holman commented Aug 20, 2013

Does #319 fix this for any of you?

@maddox
Copy link
Member

maddox commented Aug 20, 2013

I meant to check on my prod box.

I'll report back.

On Aug 19, 2013, at 10:24 PM, Zach Holman notifications@github.com wrote:

Does #319 fix this for any of you?


Reply to this email directly or view it on GitHub.

@javierburongarcia
Copy link
Author

I'm afraid not for me, it still fingerprints font assets and doesn't include the fingerprinted path in the css.

@yonjinkoh
Copy link

@javierburongarcia did you end up finding a solution for this?

@karouf
Copy link

karouf commented Dec 15, 2014

If anyone is still looking at this, I had it working by moving sass-rails and compass-rails gems out of the assets group in the Gemfile and downgrading sprockets to 2.11.0 (as per sstephenson/sprockets#540)

@karouf
Copy link

karouf commented Dec 15, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants