Possible issue with missing fa-v4compatibility font files (404 errors)

Hello,

I’ve noticed an issue in the latest version of the plugin related to the bundled Font Awesome assets.

The plugin loads Font Awesome locally (not via CDN), and in ./css/all.css there is a @font-face declaration referencing the following files:

CSS

@font-face {
font-family: 'FontAwesome';
font-display: block;
src: url("../webfonts/fa-v4compatibility.woff2") format("woff2"),
url("../webfonts/fa-v4compatibility.ttf") format("truetype");
unicode-range: U+F041,U+F047,U+F065-F066,U+F07D-F07E,U+F080,U+F08B,U+F08E,U+F090,U+F09A,U+F0AC,U+F0AE,U+F0B2,U+F0D0,U+F0D6,U+F0E4,U+F0EC,U+F10A-F10B,U+F123,U+F13E,U+F148-F149,U+F14C,U+F156,U+F15E,U+F160-F161,U+F163,U+F175-F178,U+F195,U+F1F8,U+F219,U+F27A;
}

However, the corresponding files (fa-v4compatibility.woff2 and fa-v4compatibility.ttf) are not present in the ./webfonts/ directory of the plugin.

This results in repeated 404 errors in the browser console. While the plugin still works functionally, these missing assets can trigger issues with security systems (e.g., ModSecurity and similar) and generate unnecessary log noise.

It seems this may have been introduced during the upgrade from Font Awesome 5.15.4 to 6.4.2 (v4.1 of the plugin), where the CSS was updated but not all required webfont files were included.

Suggested actions:

• Include the missing fa-v4compatibility.* font files in the /webfonts directory, or
• Remove the unused @font-face declaration if v4 compatibility is not required, or
• Load Font Awesome from a CDN instead of bundling incomplete local assets or at least allow it via config.

Much thanks for your work maintaining the plugin.