Best Premium and Free WordPress Themes › Forums › Medical Circle Pro › Graphics missing on some browsers
- This topic has 12 replies, 2 voices, and was last updated 4 years, 11 months ago by
Acme Themes.
-
AuthorPosts
-
June 11, 2018 at 9:57 pm #31093
Farren Constable
ParticipantI’m using Medical Circle Pro at alteca.com. On some computers, the little graphic icons next to “Call Us”, “Send us an eMail” and “Our location” are not displaying. Also, the left and right arrows on the slider images are not displaying. I’ve seen the problem on both Firefox and Chrome. I’ve not been able to figure out what the common quality is on the computers that have the problem. Any ideas? I could send a screenshot if that would help.
June 12, 2018 at 9:16 am #31108Acme Themes
KeymasterHello shanson,
In you site, we found following console warning, which is preventing to load fonts:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://wp.alteca.com/wp-content/themes/medical-circle-pro/assets/library/Font-Awesome/fonts/fontawesome-webfont.woff2?v=4.7.0. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://wp.alteca.com/wp-content/themes/medical-circle-pro/assets/library/Font-Awesome/fonts/fontawesome-webfont.woff?v=4.7.0. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://wp.alteca.com/wp-content/themes/medical-circle-pro/assets/library/Font-Awesome/fonts/fontawesome-webfont.ttf?v=4.7.0. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
That is actually server issue.
We wonder if you have just migrate the site fromwp.alteca.com
We have collected some information for you
http://stackoverflow.com/questions/26125030/font-awesome-icons-not-showing-in-chrome-a-maxcdn-related-cross-origin-resource
https://www.prestashop.com/forums/topic/345555-solved-glyphicons-font-awesome-not-correctly-displayed-in-firefox/We hope it will help you.
Best Regards,
AcmeThemesJune 12, 2018 at 1:55 pm #31113Farren Constable
ParticipantThanks! I will check out the info at the links you provided.
I didn’t actually move WordPress. It was built on a dedicated server at wp.alteca.com. When I was ready to take it live, I pointed the DNS record for alteca.com to the IP address of wp.alteca.com. It seemed to work — my lack of experience with WordPress is showing! Since it’s only having the problem with certain computers, I wouldn’t have associated the problem with moving WordPress.
-Farren
June 13, 2018 at 5:35 am #31121Acme Themes
KeymasterCan you add this on your .htaccess file
# Allow access from all domains for webfonts. # Alternatively you could only whitelist your # subdomains like "subdomain.example.com". <IfModule mod_headers.c> <FilesMatch "\.(ttf|ttc|otf|eot|woff|font.css|css)$"> Header set Access-Control-Allow-Origin "*" </FilesMatch> </IfModule>
Thanks!
June 14, 2018 at 9:41 pm #31193Farren Constable
ParticipantThat doesn’t seem to have made a difference. Or, I did it wrong….
-Farren
June 15, 2018 at 8:54 am #31221Acme Themes
KeymasterHello Farren,
We would like to suggest you to contact your hosting provider for this issues.
Best Regards!
June 18, 2018 at 9:17 pm #31326Farren Constable
ParticipantWell, for all practical purposes, I’m the hosting provider. I’m “renting” a server but I’m 100% responsible for what’s run on that server. It’s NOT a shared server. So, if there’s an OS configuration change that needs to be made, I’ll be the one doing it. The OS is the latest Open SuSE.
So the question is, what needs to change in the OS?
-Farren
June 19, 2018 at 5:21 am #31330Acme Themes
KeymasterHello,
This should fix this issue
If this doesnot fix , we recommended you to contact hosting expert.
Thanks
June 29, 2018 at 5:40 pm #31712Farren Constable
ParticipantI’m confused by that last post — what was it supposed to link to? It seems to only link back to this thread.
-Farren
July 1, 2018 at 12:35 pm #31751Acme Themes
KeymasterDid you added this code on your .htaccess file.
# Allow access from all domains for webfonts.
# Alternatively you could only whitelist your
# subdomains like “subdomain.example.com”.
Header set Access-Control-Allow-Origin “*”
You can find similar query on searching Eample https://stackoverflow.com/questions/11616306/css-font-face-absolute-url-from-external-domain-fonts-not-loading-in-firefox
Best Regards!
July 2, 2018 at 8:40 pm #31791Farren Constable
ParticipantMy .htaccess file is as follows:
# Allow access from all domains for webfonts.
# Alternatively you could only whitelist your
# subdomains like “subdomain.example.com”.
<IfModule mod_headers.c>
<FilesMatch “\.(ttf|ttc|otf|eot|woff|font.css|css)$”>
Header set Access-Control-Allow-Origin “*”
</FilesMatch>
</IfModule>as per the example you gave earlier.
-Farren
July 2, 2018 at 8:55 pm #31792Farren Constable
ParticipantBut…. I failed to check to make sure mod_headers was loaded. It wasn’t… It is now, and the icons/graphics are loading.
Thanks!
-Farren
July 3, 2018 at 4:01 pm #31814Acme Themes
KeymasterGreat to know your problem solved.
Best Regards!
-
AuthorPosts
- You must be logged in to reply to this topic.