This topic has 15 replies, 4 voices, and was last updated 9 years, 11 months ago ago by Robert Hall
Recently I change my WordPress Site address (from http://www.serpentina.mx/site to http://www.serpentina.mx) but everything worked right but the AwesomeFont icons started to fail. I need help to fix it, please check my site and help me to fix this issue.
Hello,
Please provide us with wp-admin access in Private Content.
Regards,
Robert Hall.
Ok, thanks for your help
Hello,
is your site currently online? We can not reach it
Regards,
Stan Russell
Yes, the site is http://www.serpentina.mx
Hello,
Could you please show us a screenshot of the issue to have clear understanding?
Thank you.
Regards,
Eva Kemp.
Yes.
As you can see on this screenshot, the arrows that help to navigate between products are gone, instead the page shows two squares, the same happen with the up arrow of the “back to top” button.
https://www.dropbox.com/s/wdsgkv18umkf52a/Captura%20de%20pantalla%202014-12-12%2020.18.44.png?dl=0
Hello,
As I see the arrows are shown on a single product page:
Try to check it in some other browser.
What theme version are you using?
Regards,
Eva Kemp.
I checked on another computer, on Chrome the problem is there, on Explorer appear to be blank circles.
I’m using 1.5.2 version
Hello,
Does this problem persists for all pages?
Are other icons displayed?
Do you have any restrictions on a server or in your .htaccess file as we can access wp-admin panel? It isn’t loading.
Thank you.
Regards,
Eva Kemp.
Yes, the problem persists for all pages
All the icons are gone
I don’t have any restrictions
Hello,
The problem is caused by site movement:
http://gyazo.com/3c851832f193999a36d03c704a9441d0
You can fix this issue adding the code <link href="//maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css" rel="stylesheet">
in header.php file before closing tag </head>
.
Regards,
Eva Kemp.
Thanks! Now is working.
Hello,
You’re welcome!
Regards,
Robert Hall.
The issue related to '‘Problem with FontAwesome icons’' has been successfully resolved, and the topic is now closed for further responses