I can’t seem to be able to reproduce the issue on my end. I wonder if this could be caused by the CDN you use on WPEngine. Does WPEngine allow you to exclude specific files from its CDN, and serve them locally instead?
If so, could you try to remove all files in /wp-content/plugins/jetpack/_inc/social-logos/, and let me know if it helps?
Thanks!
WPE support can exclude paths from the CDN. If you ask support to add ^/wp-content/plugins/jetpack/_inc/social-logos/ to your “Don’t load from CDN” rules in chat βΒ and then flush your cache β they can help you test this theory pretty quickly.
-
This reply was modified 9 years, 8 months ago by
Jason Cosper.
I tried contacting WP Engine. They set a rule to ignore, but that didn’t work.
I contacted WordPress Support and this is what they said below. I guess I have to switch the theme to see if that’s the issue.
———- Forwarded message ———-
From: Rachel M [removed]
Date: Fri, Sep 23, 2016 at 9:25 AM
Subject: [#2842795]: Jetpack – Support message
To: info@melibeeglobal.com
Hi there,
Thanks for contacting us! I tested this in my own web browser (I use Opera) and can see the error messages in the console. I also tried in Chrome and Firefox and they’re not displayed in Firefox. It looks to be related to this Chrome issue:
https://github.com/ntop/ntopng/issues/121
I also tried testing it on my test blog and I don’t have the same error messages in the console for the sharing buttons on my site:
https://rachelsquirrel.mystagingwebsite.com/2016/09/jump-2/
You could try adding the opentype (OTF) url of the font as specified in the last comment on the Github page to your theme’s css or wherever the fonts are specified. To verify that it is the theme, try changing to Twenty Sixteen temporarily to see whether the issue persists.
-
This reply was modified 9 years, 8 months ago by
James Huff. Reason: email address removed
I tried contacting WP Engine. They set a rule to ignore, but that didnβt work.
The file still appears to be served via the CDN. Did they revert that change after your tests?
Yes, they reverted back.
I can have them restore the rule and then you can test it again.
-
This reply was modified 9 years, 8 months ago by
Tony Zeoli.
If that’s possible, that’d be nice. Let me know when they’ve made the change!
Thanks!
Okay, they’ve restored the rule to ignore. Let me know what you find out.
The files are still served from the CDN. Could you try to purge your site’s cache?
Oh, sorry about that. Purged WP Engine and Cloudflare caches.
The resources are still served from the CDN on my end. Could you check if you see the resources as served from your local site on your end?
Okay, now the resources are served from the melibeeglobal.com domain. That’s all set. They wrote a cache rule and a post processing rule to ensure that it’s served from the domain. You can now see in the javascript console the social icons are being served from the melibeeglobal.com domain.
Thank you. I can see the problem is still there. At this point, I’m afraid I don’t know what could be causing this. I think we might be running into this bug, but I don’t understand why I can’t reproduce on other sites.
Would you mind contacting us via this form, and mention this thread? I’d like to run some more tests with you to figure this out.
Thanks!
Okay, will do.
This is also now happening at NerdHives.com, another site I’m working on for a client, too.
It’s interesting that this would happen on 2 of the sites you’re working on. Do the sites share common plugins? How did you install Jetpack on those 2 sites? Did you go through the usual Plugins > Add New, or did you somehow copy the plugin from somewhere else?
To close the loop on this, it appears that this was a conflict between Jetpack’s Social Logos and The Make theme. The theme authors will fix the issue in their next release, but until then, this little CSS snippet should solve the problem for everyone experiencing the same problem:
.share-icon {
text-rendering: auto;
}