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.

Replies

5
  1. Andrew Misplon Staff 7 years, 6 months ago

    Hi

    The problem is caused by loading WordPress from a different domain. See: https://davidwalsh.name/cdn-fonts. If at Settings > General your Site and WordPress URL’s are the same, this issue wouldn’t occur. Be careful when making any changes at Settings > General and make sure your server setup is correct before adjusting the URL’s.

  2. Александр Бакалов 7 years, 6 months ago

    >>If at Settings > General your Site and WordPress URL’s are the same, this issue wouldn’t occur. Be careful when making any changes at Settings > General and make sure your server setup is correct before adjusting the URL’s.

    There the addresses (URL’s) are the same, absolutely identical.

    >>https://davidwalsh.name/cdn-fonts
    I’ll try to do it in the evening.

  3. Andrew Misplon Staff 7 years, 6 months ago

    The domain your assets are being loaded from is: http://u0519096.plsk.regruhosting.ru/aeroturplus.ru/wp-content/plugins/so-widgets-bundle/widgets/features/css/style.css?ver=1.12.1 but your domain is http://aeroturplus.ru/. That causes the CORS issue. If you open up your browser’s developer console you’ll see the console errors that result from this. If your WordPress and Site URL are the same then it’s something your host is doing.

  4. Александр Бакалов 7 years, 6 months ago

    I can not solve this problem, because I have Windows hosting :(
    I tried this: https://davidwalsh.name/cdn-fonts, but it did not help. In the comments there is a way for Windows hosting, but the problem does not solve. (configuration in web.config)

  5. Andrew Misplon Staff 7 years, 6 months ago

    The root cause of the issue is your files not being hosted at the same URL as your Site URL, I don’t think that aspect of the problem is Windows specific, that possibly a host level problem.

    Cross domain issues like this would present even if you self hosted Font
    Awesome and added your own custom CSS so from that perspective it isn’t specific to the SiteOrigin Widgets Bundle.

    My advice would be to chat your hosts and focus on your files being hosted at a different URL to your site. That isn’t common. If your Site and
    WordPress URL’s are the same then I’m not sure why that’s the case. Perhaps download your wp-config.php file and see what’s happening there.

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