404's on Fonts
See original GitHub issueI 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!
Issue Analytics
- State:
- Created 7 years ago
- Comments:25 (11 by maintainers)
Top Results From Across the Web
font-face returns 404s on fonts - Stack Overflow
I've tried to set up a custom font for my website, but it doesn't work neither on Firefox, Chrome or Edge/IE. The network...
Read more >woff files are returning 404s · Issue #1642 · google/fonts - GitHub
I'm currently using Firefox Developer Edition 62.0b16 and noticed that the following URL returns a .css file that instructs the browser to ...
Read more >[HELP] Fonts not being found 404 error - even though they're ...
On build they get copied perfectly to the dist dir but the CSS can't reference them. I just get 404s in the console....
Read more >IIS7 Serving Font Files as 404s - Server Fault
I'm having trouble getting font files to be returned by my IIS. The URLs are correct, the mime-types are set correctly, but I'm...
Read more >WebSite Auditor: 404 error for fonts.googleapis.com ... - Drupal
Do you ever notice any 404s for fonts when using Chrome, Firefox, IE, Opera, etc? As for dns prefetch, once this issue is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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
materialize
in 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