This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

font awesome icons not showing in firefox and chrome

Resolved 3 replies pluginplugin-widgets-bundletechnical
martin.s
9 years ago · Last reply by Alex S 9 years ago

Hi there,

I was so happy to have found your widgets bundle and have used the site origin features widget to display font awesome icons.

After a day I found out, that I can well see them in safari but not in chrome or firefox. I have read through the threads here and it seems like a problem that has been happening before. Unfortunately I just don’t get how to solve it.

I also cloned the site (for testing purposes) and AFTER cloning it, it actually worked. But I need the original url to work. So I am wondering if someone would be so nice and help. English is not my native language so maybe i need a little longer …

Thank you in advance – and what UI wanted to say – I really like your plugins!

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

3
  1. Alex S Staff 9 years, 7 months ago

    Hi Martin,

    Thank you for the kind words. :)

    I suspect this is a CORS issue.

    Do you have a public URL where we can take a look and either confirm this or find what the real issue is? If you need to keep this URL private from other users, just select “Private Reply” on the bottom right of the comment box.

  2. martin.s 9 years, 7 months ago

    Hi Alex,

    thank you for getting back with me. I searched and searched and found the solution myself. It was actually related to the settings that I have entered with my ISP. I had two domains pointing to a directory (an .de and a .org domain). So instead of redirecting it to one and the same url the site was not behaving g consistently. I changed it and now it works ….

    Thanks again!

    Best Regards

    Martin

  3. Alex S Staff 9 years, 7 months ago

    Hi Martin,

    So yeah that’s definitely a CORS issue then. Glad you managed to work it out mate. :)

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread