ember-cli-materialize: 404's on Fonts
I have started getting 404’s when my app is looking for the Roboto font using this add-on. I’m not sure if this is related to attemping to upgrade the package (I’ve tried going back a version, but after rm -rf tmp dist I’m still having issues).
The materialize CSS file appears to be pointing the browser here:
/fonts/roboto/Roboto-Regular.woff
However, the default ember-cli-materialize build looks to be putting them at the top-level under /assets.
Any help would be appreciated!
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 25 (11 by maintainers)
Commits related to this issue
- Fixes #327 - Run dependent addon installation blueprints (derp) — committed to mike-north/ember-cli-materialize by mike-north 8 years ago
- Fixes #327 - Run dependent addon installation blueprints (derp) (#336) — committed to ChristianGreinke/ember-cli-materialize by mike-north 8 years ago
Alright, I have a much cleaner fix for you guys 😃
We are in luck that the Materialize guys have parameterized their font path.
All you need to do is define a different path before importing
materializein your app.scss file.Example:
I’ll update the installation blueprint and cut a new release so that others don’t run into this same problem
Thanks for the info guys. I think I can track this down now. Appreciate your patience
@lukeclewlow thanks, I did the same and it fixed the issue. Hopefully this helps others.
@allthesignals I had the same problem, it seems that materialize renamed their file structure at some point like you thought from
fonttofonts. I ranbower install materialize#0.97.1and it has fixed the problem for me. The blueprint installs~0.97.0which now defaults to0.97.8which is after the change.To get the fonts to work, I added following to node_modules/ember-cli-materialize/index.js