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

Glyphicons are not working in production #62

Closed
michaelkoper opened this issue Oct 24, 2013 · 6 comments
Closed

Glyphicons are not working in production #62

michaelkoper opened this issue Oct 24, 2013 · 6 comments

Comments

@michaelkoper
Copy link

In development they are working fine but in production they look like squares. Am I doing something wrong here? Or do I have to manually include them myself?

Im using Rails 4 with bootstrap-sass-rails-3.0.0.3.

@daniel-illi
Copy link

I experience the same problem.
The hash of the font files referenced in the generated css does not match the hash of the filenames of the font files, so the files can not be found on the server (HTTP 404 Error).

@michaelkoper
Copy link
Author

I dont have time to fix this at this moment so I came with a dirty work around instead :-)

I copied the fonts and put them in the public folder under twitter/bootstrap

I added the url with !important

@font-face
font-family: 'Glyphicons Halflings'
src: url("/twitter/bootstrap/glyphiconshalflings-regular.eot") !important
src: url("/twitter/bootstrap/glyphiconshalflings-regular.eot?#iefix") format('embedded-opentype') !important
src: url("/twitter/bootstrap/glyphiconshalflings-regular.woff") format('woff') !important
src: url("/twitter/bootstrap/glyphiconshalflings-regular.ttf") format('truetype') !important
src: url("/twitter/bootstrap/glyphiconshalflings-regular.svg#glyphicons_halflingsregular") format('svg') !important
font-weight: normal
font-style: normal

@yoyos
Copy link

yoyos commented Nov 8, 2013

Same issue here.
And I would like to use them in production but rake:precompile generates them with a hash.

@verdi327
Copy link

Experiencing the same issue as well

@mjonuschat
Copy link
Owner

Has anybody a sample application that I can put up on Heroku to test this, I can't seem to reproduce this at the moment.

@mjonuschat
Copy link
Owner

Since I can't reproduce this I'll close this bug. That the font-files get fingerprinted is normal for the asset pipeline. As the SCSS Files use font-url() the fingerprinted version of the fonts will be used in the combined/compressed CSS output. Please re-open if there is a way to reproduces this.

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

5 participants