August 23, 2017 at 7:41 am #7608
In the last few days I’ve found the arrows for my drop-down menus aren’t displaying, and neither are the social links in my bottom bar. This only seems to happen if I don’t use the https: URL to visit the site.
But when I access via https it displays correctly.
I can use https reliably, it seems, so I suppose it’s not the end of the world. Is this something that’s happening through Puro, or is it a server (or client-side) problem?
BenAugust 23, 2017 at 10:43 am #7609
This is probably what’s happening. Browsers block assets that aren’t from the same domain, you can read more about that issue here:
Settings > General. There shouldn’t be an issue if your URL’s are the same. If your Site and WordPress URL differ it will cause a CORS error and the theme’s web fonts won’t be allowed to load. If your Site URL doesn’t have https and your WordPress URL does it will cause assets to be blocked.
(It’s best to run your site on
https.)August 23, 2017 at 10:49 am #7610
If you access your site via
httpyou can see the error. Open the developer tool in your browser, click over the console and it’ll be there.
Access to Font at 'https://www.berkeleysquarecopywriting.com/wp-content/themes/ultra/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0' from origin 'http://www.berkeleysquarecopywriting.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.berkeleysquarecopywriting.com' is therefore not allowed access.
Your site should be forwarding all
httpqueries to the
httpsversion, it shouldn’t be possible to access both versions.
Plugin to use:August 24, 2017 at 3:48 pm #7612
Thanks very much for your reply, and for the useful info. The site is now forwarding http to https, so I’m not sure why it wasn’t doing so temporarily.
In any case, so long as it isn’t a permanent issue there’s no worries.
Thanks once again for your quick and accurate assistance!
BenAugust 24, 2017 at 3:49 pm #7613
Awesome 🙂 Glad to hear everything is going to https now.
You must be logged in to reply to this topic.