Lỗi fontawesome-webfont.woff2 v 4.7.0 net err_aborted 404 not found năm 2024

After installing ShortPoint Farm Solution to your SharePoint Farm you notice following error in browser console:

Error you are getting:

shortpoint.master.js GET http://portal/layouts/15/ShortPoint.Foundation/UI-Core/fonts/fontawesome-webfont.woff2?v=4.3.0 net::ERR_ABORTED 404 (Not Found) getScrollWrapper @ shortpoint.master.js?version=5.4.0.32:60577 init @ shortpoint.master.js?version=5.4.0.32:70755 init @ shortpoint.master.js?version=5.4.0.32:81177 (anonymous) @ shortpoint.master.js?version=5.4.0.32:59990 tryCatch @ shortpoint.master.js?version=5.4.0.32:54499 (anonymous) @ shortpoint.master.js?version=5.4.0.32:59976 .each..forEach @ shortpoint.master.js?version=5.4.0.32:44685 applyShortPointToElement @ shortpoint.master.js?version=5.4.0.32:59922 parseElement @ shortpoint.master.js?version=5.4.0.32:60057 (anonymous) @ shortpoint.master.js?version=5.4.0.32:60312 .each._.forEach @ shortpoint.master.js?version=5.4.0.32:44680 init @ shortpoint.master.js?version=5.4.0.32:60304 (anonymous) @ shortpoint.master.js?version=5.4.0.32:60336 fire @ shortpoint.master.js?version=5.4.0.32:4592 fireWith @ shortpoint.master.js?version=5.4.0.32:4704 ready @ shortpoint.master.js?version=5.4.0.32:1977 completed @ shortpoint.master.js?version=5.4.0.32:1648 load (async) jQuery.ready.promise @ shortpoint.master.js?version=5.4.0.32:2479 ready @ shortpoint.master.js?version=5.4.0.32:1815 init @ shortpoint.master.js?version=5.4.0.32:1758 jQuery @ shortpoint.master.js?version=5.4.0.32:1607 (anonymous) @ shortpoint.master.js?version=5.4.0.32:5011 (anonymous) @ shortpoint.master.js?version=5.4.0.32:5107 window.shortpoint_master_run @ shortpoint.master.js?version=5.4.0.32:11333 (anonymous) @ NewHome.aspx:251

Reason

ShortPoint is using fonts with extension woff2 which are by default not supported in IIS and hence they get blocked by your SharePoint server.

I went to Theme Setting >> Performance and turn OFF the minification of the CSS and JS and save changes and then checked the site after removing the browser cache, all the issues are resolved, and that minification creates issue because you are using many of the third party plugins and it conflict with any one of them that is the reason it was creating an issue on your site.

I'm not sure if this is a mime-type related issue with my server configuration or an error with this module, but I'm getting the following error message in the Chrome console for most pages on my site:

Failed to load resource: the server responded with a status of 404 (Not Found) libraries/fontawesome/fonts/fontawesome-webfont.woff2?v=4.3.0

I've attached an image of both the console error message as well as the Drupal log message. I noticed that this module automatically pulls the library from a cdn, so there isn't really an easy way for me to prevent the css file from trying to load the woff2 file, but the better approach I feel is for me to simply figure out what's causing the error and fix it straight away.

Support from Acquia helps fund testing for Drupal

I am running Firefly III version 4.7.1.2, just upgraded from 4.7.0 (also made sure to follow the new upgrade steps).

Description of my issue:

After upgrading, the layout was broken in Firefox because it didn't have the proper path for the Font Awesome fonts. Even though I could also see the 404s in Chrome dev tools, the layout didn't break in Chrome. I was able to fix it by changing these URLs in /public/css/app.css from this:

@font-face{font-family:FontAwesome;src:url(/fonts/vendor/font-awesome/fontawesome-webfont.eo
t?674f50d287a8c48dc19ba404d20fe713);src:url(/fonts/vendor/font-awesome/fontawesome-webfont.eot?
674f50d287a8c48dc19ba404d20fe713) format("embedded-opentype"),url(/fonts/vendor/font-awesome/fo
ntawesome-webfont.woff2?af7ae505a9eed503f8b8e6982036873e) format("woff2"),url(/fonts/vendor/fon
t-awesome/fontawesome-webfont.woff?fee66e712a8a08eef5805a46892932ad) format("woff"),url(/fonts/
vendor/font-awesome/fontawesome-webfont.ttf?b06871f281fee6b241d60582ae9369b9) format("truetype"),url(/fonts/vendor/font-awesome/fontawesome-webfont.svg?912ec66d7572ff821749319396470bde) format("svg");font-weight:400;font-style:normal}

To this:

@font-face{font-family:FontAwesome;src:url(../fonts/vendor/font-awesome/fontawesome-webfont.eo
t?674f50d287a8c48dc19ba404d20fe713);src:url(../fonts/vendor/font-awesome/fontawesome-webfont.eot?
674f50d287a8c48dc19ba404d20fe713) format("embedded-opentype"),url(../fonts/vendor/font-awesome/fo
ntawesome-webfont.woff2?af7ae505a9eed503f8b8e6982036873e) format("woff2"),url(../fonts/vendor/fon
t-awesome/fontawesome-webfont.woff?fee66e712a8a08eef5805a46892932ad) format("woff"),url(../fonts/
vendor/font-awesome/fontawesome-webfont.ttf?b06871f281fee6b241d60582ae9369b9) format("truetype"),url(../fonts/vendor/font-awesome/fontawesome-webfont.svg?912ec66d7572ff821749319396470bde) format("svg");font-weight:400;font-style:normal}

I was going to try and submit a PR, but I wasn't sure where that part of app.css got pulled in from (perhaps one of the vendor packages?)