Out of the clear blue a few days ago, the ribbon bar across the top of the the post editor lost it's old icons and is now displaying this. {} It's happening with all the 2014 and 2016 themes. If I switch to the retro theme, intelligible icons return. {} This is happening with Safari under iOS on an iPhone, and both Chrome and Firefox on my laptop under Linux. So whatever is causing it is not machine specific. Are you using a webding font for the icons now? If so, could you tell me what font that is so I can load it and fix this. Otherwise, do you have any suggestions for how to get back the icons that were there a few days ago ? Thx.
We've been using Font Awesome for the editor icons for a year and a half now... no recent changes. Maybe in Chrome, open your developer tools window, and check the console for any errors, and your network tab as well. You should be loading Code: https://maxcdn.bootstrapcdn.com/font-awesome/4.6.3/css/font-awesome.min.css Very weird that it happens on your iphone too...
It gets even weirder. Now it's working again. Ok...now I see where the problem might be. If I web out to your bootstrap.com CSS the browsers I get an alert. https is having an issue with Code: https://maxcdn.bootstrapcdn.com/font-awesome/4.6.3/css/font-awesome.min.css . It reports: NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED Chrome 53 and up now require net transparency. I guess Bootstrapcdn got their certificate sufficiently fixed in the meantime.
Spoke too soon. Closed the browser and then came back and it switched back. Had to open the CSS in another tab and tell Chrome to ignore the error. Now the icons are ok again. But https is now disabled in my browser for your site because I allowed a mixed content override on the script. {} {}
That's really weird. I've never had any issues with the maxcdn.bootstrapcdn certificate, and have had no other user reports of this error.
If it's any consolation, it stopped about 12 hours afterwards and now works fine. I did a little research on my end and found there have been some issues with our ISPs where I am. We were getting weird DNS problems previously so I'm suspecting something on the ISP's end might be behind it all. Either way, it works fine now. Stopped as abruptly as it started. Weird.
Here are some related products that TB members are talking about. Clicking on a product will take you to TB’s partner, Primary, where you can find links to TB discussions about these products. Browser not compatible
