5.0.4 doesn't show font icons
See original GitHub issueDescribe the bug
When using https://cdn.conversejs.org/5.0.4/dist/converse.min.css
and https://cdn.conversejs.org/5.0.4/dist/converse.min.js
no icons are shown. If I use 5.0.3, everything runs smoothly.
To Reproduce Steps to reproduce the behavior:
- Install via Github releases (https://conversejs.org/docs/html/quickstart.html#option-2-download-the-builds-from-github)
- Load current version of
converse.min.[css|js]
and put into/dist
- You don’t see any icons
Screenshot
Expected behavior I should see icons.
Environment (please complete the following information):
- Desktop or Mobile - both
- Browser: Safari, FF, Chrome
- Converse.js version: 5.0.4
Additional context index.html.j2
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Font Awesome 5 Icons not Showing? - Slick Media
Font Awesome has evolved considerably over the years and in some cases this has led to changes and breaks in the Unicodes. So,...
Read more >Font Awesome 5 icons not showing up - Stack Overflow
I use codeigniter and Font Awesome 5 I have download the latest version of font awesome 5 how ever for some reason my...
Read more >Troubleshooting | Font Awesome Docs
Typically this is due to a local network configuration issue or an issue with the ISP. Some of the steps to troubleshoot this:...
Read more >How to Fix Font Awesome Icons Showing as Box? - WebNots
Struck with font awesome icons showing as box? Here are the reasons why you see box and solutions to fix the icons showing...
Read more >How To Fix Missing Font Awesome Icons Or Custom Fonts
Another scenario when the Font Awesome icons do not show, is when no Font Awesome font subset is selected in the Theme Features...
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
I solved it by adding this to the location in nginx:
location ~* .(eot|ttf|woff|woff2)$ { add_header Access-Control-Allow-Origin *; }
@mase76 Check the network tab in the browser console to see at which path Converse is trying to load the webfonts. That can help you debug what’s going on.