I was also having issues with Wordpress on a separate subdomain, but that was a PHP config issue, not a Backlight issue. In my case, I had to enable mod_headers on my server to solve CORS problems.
@PhotOne Contact me privately, and I’m sure we can work something out to get you upgraded. The icons issue is my own fault – the decision to handle Font Awesome as I did in B4 seemed sensible at the time, but ultimately was a mistake. I definitely don’t want you to have insurmountable problems because of that bad decision.
Is that something that can be done from the C-Panel?
Depends on the cPanel, I guess. My server is self-managed, so I don’t have a cPanel. I had to enabled it from the command line, using a sudo command.
@Ben advised that one way to test whether mod_headers is enabled, is to put junk within the tags in the .htaccess file, and see whether the server return a 500 error.
<IfModule mod_headers.c>
asdf
</IfModule>
I should emphasize that if Backlight and Wordpress are running in the same space, this shouldn’t be an issue. This was only a problem for me because I have them running on separate subdomains, theturninggate.net and blog.theturninggate.net.
The issue was essentially that blog.theturninggate.net was unable to load assets from theturninggate.net.
added the code and the server threw the error
Sounds like mod_headers is enabled then, so our two issues are probably not the same.
Hm. Or maybe just the solution will be different. I’m looking at Font Awesome 5 Free Unicode Fix - TTG Tips and Tricks now, and those are definitely the same CORS errors that I was seeing.
this is happening in a couple of sites.
In my main site blog, which is in a sub-folder
And my ttg-tips site, in a sub-domain and based on WordPress.
In both sites, the front page is working fine, all icons are showing. It’s when you get to the posts or other pages within the blog or site.
My workshops site is also in a sub-domain and is based on WordPress. It consists mostly of pages. I have no missing icons in that site at all.
I’ve tried disabling plugins.
GET https://www.paypalobjects.com/en_US/i/scr/pixel.gif net::ERR_BLOCKED_BY_CLIENT
ttg-tips-and-tricks.barbeephoto.com/:615
GET https://bluehost-cdn.com/media/partner/images/rodbarbee/300x250/bh-ppc-banners-dynamic-300x250.png net::ERR_BLOCKED_BY_CLIENT
These two errors, I suspect you may need either to add ttg-tips-and-tricks.barbeephoto.com to a whitelist at each source, else you’ll need to set up your subdomains separately, and handle them both in your PHPlugins functions, wherever these are being used.
These errors:
Access to font at 'https://ttg-tips.com/backlight/modules/module-admin/lib/webfonts/fa-solid-900.woff2' from origin 'https://ttg-tips-and-tricks.barbeephoto.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
all.min.css:1
GET https://ttg-tips.com/backlight/modules/module-admin/lib/webfonts/fa-solid-900.woff2 net::ERR_FAILED 200
… I would expect to be solved on your own server, however the CORS errors end up being addressed.
I don’t know whether this will work, but worth trying:
tried a few of them. Not sure I did it right. I did remember to insert my domain name at least 
None of them worked. But none of them broke anything either.
Might be worth firing some questions at host support. CORS policy issues can be tough to sort out.
1 Like
I think I fixed it.
The original url for my site is barbeephoto.com. Years ago, I bought another domain name, rodbarbee.com and assigned it. So you can get to the site with either url.
In Backlight, I set the site url to rodbarbee.com.
For my blog, in WordPress settings, I still had barbeephoto.com/blog as the WordPress and site url.
Changed those to rodbarbee.com and now all the Font Awesome icons are appearing.
Same basic problem with my ttg-tips site. It’s in a sub-domain: ttg-tips-and-tricks.barbeephoto.com. That was the address used in WordPress General settings.
But in Backlight, I use ttg-tips.com as the site url.
For both sites, if I went to the home page using the shorter address (rodbarbee.com or ttg-tip.com), the home page of either the blog or the ttg-tips site looked good. When going to pages or posts, the older urls were used and the icons disappeared.
Changing WordPress settings so that they matched Backlight settings fixed it all.
I guess that’s the difference between Font Awesome being source from the Font Awesome servers versus hosting it locally.
1 Like