![\"\"](\"https:\/\/easy-admin.ca\/wp-content\/uploads\/2017\/01\/icon-not-showing.png\"){kind=icon}
<\/p>\n<\/p>\n
The icons \u2013 including submenu indicator arrows \u2013 for example in UberMenu are font icons. Some browsers \u2013 most commonly Firefox \u2013 enforce a Cross-origin resource sharing (CORS) restriction policy for fonts. As a result, if you serve the Font Awesome fonts from a separate domain, Firefox (and depending on your server configuration, other browsers as well), will not load the fonts due to this policy, so the icons are not displayed.<\/p>\n
The most common occurrence is using a CDN. For example, if your site is There are two options to resolve the issue: either serve your fonts from the same domain as your site, or configure the fonts on your secondary domain to be served with the appropriate headers to allow cross-origin resource sharing.<\/p>\n This generally means that you would exclude the Font Awesome files from your CDN, and link the files on your main server instead. The font file itself is the important resource, but generally this would come down to excluding the Font Awesome stylesheet. If you\u2019re using UberMenu\u2019s copy, it is found at<\/p>\n This solution will work, but you won\u2019t be able to take advantage of your CDN for these files.<\/p>\n This means that you would configure your server to tell the browser that it\u2019s okay to load these resources from a different domain.<\/p>\n What you\u2019ll need to do is set the <FilesMatch “.(eot|ttf|otf|woff)”><\/strong> You may have to check your Theme directory if you are not using UberMenu’s Font Awesone…<\/strong><\/p>\n wp-content\/themes\/theme_name\/fonts<\/strong><\/span> and simply add the file UberMenu\u2019s Font Awesome assets are located in [Experimental] for SSL website<\/strong><\/p>\n Header add Access-Control-Allow-Origin “https:\/\/www.domain.com” The icons \u2013 including submenu indicator arrows \u2013 for example in UberMenu are font icons. Some browsers \u2013 most commonly Firefox \u2013 enforce a Cross-origin resource sharing (CORS) restriction policy for fonts. As a result, if you serve the Font Awesome fonts from a separate domain, Firefox (and depending on your server configuration, other browsers … Continue reading Website Icon Not Showing Up?<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1011","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/posts\/1011","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/comments?post=1011"}],"version-history":[{"count":0,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/posts\/1011\/revisions"}],"wp:attachment":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/media?parent=1011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/categories?post=1011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/tags?post=1011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}mydomain.com<\/code>, but your stylesheets are served from cdn.mydomain.com<\/code>, or cdn.someotherdomain.com<\/code>, the browser will not load the fonts because they are served from another domain.<\/p>\nThe Solution<\/h4>\n
Serve the files from the same domain<\/h5>\n
\/wp-content\/plugins\/ubermenu\/assets\/css\/fontawesome\/css\/font-awesome.min.css<\/code><\/p>\nSet the font headers to allow cross-origin resource sharing<\/h5>\n
Access-Control-Allow-Origin<\/code> header to *<\/code> for the fonts. If your server is running apache, this generally just means dropping an .htaccess<\/code> file into the directory containing the font with the following configuration<\/p>\n
\n Header set Access-Control-Allow-Origin “*”<\/strong>
\n <\/FilesMatch><\/strong><\/p>\n
\n.htaccess in the directory!<\/p>\n\/wp-content\/plugins\/ubermenu\/assets\/css\/fontawesome\/fonts\/<\/code><\/p>\n![\"\"](\"https:\/\/easy-admin.ca\/wp-content\/uploads\/2017\/01\/icon-showing.png\"){kind=icon}
<\/p>\n
\n#Header add Access-Control-Allow-Origin “https:\/\/domain.com”
\nRewriteEngine On
\nRewriteCond %{HTTPS} !=on
\nRewriteRule ^\/?(.*) https:\/\/%{SERVER_NAME}\/$1 [R,L]<\/p>\n","protected":false},"excerpt":{"rendered":"