unable to load font awesome from dashboard
See original GitHub issueThe server returns an internal server error when loading some CSS files from the dashboard page. The following are the list of file not being loaded and returning 500
resources/core/resources/vendor/fontawesome/css/all.min.css
resources/core/resources/vendor/fontawesome/css/v4-shims.css
resources/core/resources/vendor/pt-sans/styles/pt_sans.css
Issue Analytics
- State:
- Created 2 years ago
- Comments:42 (22 by maintainers)
Top Results From Across the Web
Unable to load Font Awesome - Stack Overflow
I get a blank space where the fonts should appear. Here are the details: https://www.foo.com/public_html/wp-content/themes/independent- ...
Read more >Troubleshooting | Font Awesome Docs
Are you using Font Awesome Free or Pro? - Some icons are only available in Font Awesome Pro. Double-check that the icon you...
Read more >[Solved]: Font Awesome icons not showing on my website
If the Font Awesome CSS file is not properly loaded on a web page, then its icons won't be displayed. There are different...
Read more >Font awesome not loading in one page - WordPress.org
Go to Dashboard => Gutentor => Settings => Optimization => Resources Load and Select Force Load on Font Awesome. Let me know if...
Read more >Unable to load font-awesome - OpenCart Community
Hello everybody, We just created a new website and currently as we moved from a host to another we are facing some difficulties...
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 found the problem : Ajenti send a last-modified header to use the cache for css files if needed, and the date is formatted with the locale installed on the server. For RU or CN, this header then contains non-latin chars which is not allowed. So I just converted the date with en_us locale in order to send right headers.
I will test further and I hope this commit finally solves this issue.
I would not have found it by myself without your help, thanks for it.
Arnaud
Many thanks for your feedback and your positive words. So i can finally close this !
Arnaud