Activating Jetpack creates error message in the console
-
I noticed some error messages in the console that said:
downloadable font: no supported format found (font-family: “Noticons” style:normal weight:400 stretch:100 src index:1) source: (end of source list)
Loading failed for the <script> with source “https://stats.wp.com/w.js?61”.Tha last message has a link at the end, I copied it:
I deactivated all plugins and reactivated them one at a time until the error came back with Jetpack activation. How can I prevent the error? What is the cause? What is the harm?
This site is a clone of my real site as I experiment with some new ideas on it.
Thank you,
Cemal
-
This topic was modified 4 years, 3 months ago by
acekin.
-
This topic was modified 4 years, 3 months ago by
acekin.
The page I need help with: [log in to see the link]
-
This topic was modified 4 years, 3 months ago by
-
Hi @acekin
That’s definitely an error related to a font not being found, and I can see that the script that failed to load is related to the stats, are you able to access those on your WP Admin?
I’ve also looked further on that site, and found that Staging Mode was already enabled so that no data will be synced with WordPress.com. The error you had shouldn’t be harmful, but it’s better to check with the production site since that’s where you’d expect the communication and sync to work.
Best,
Thank you @muffinpeace, the same errors appear on my site as well. Since it is tied to Jetpack, I am hoping that your team will either fix it at the root or tell me how to fix it at my end. Any help will be appreciated.
Thank you,
Cemal
A related question: Is it possible that I am receiving some or all these error messages in the console because I am using an ad blocker plugin, uBlock Origin?
Cemal
Cemal,
I would say it’s worth a shot loading up the site on a different browser without adblock or a different machine altogether to see if the warning message is still there.
If everything is working normally on the site and you’re not experiencing any issues, it’s okay to ignore this non-critical warning message in your browser’s inspector.
Please let us know if you have any other questions!
@madhattersez, if I let uBlock Origin bypass my site, much of the error listings are gone. A couple of remaining ones say:
Some cookies are misusing the recommended “SameSite“ attribute
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”.And, if I am not logged in but still using Firefox:
Google Analytics and Tag Manager is being shimmed by Firefox.
is added to the others. The other error messages are not there.
I understand from your comment that I can ignore the errors when the site is visited by a visitor using something similar to uBlcok Origin, is that correct?
Thank you,
Cemal
>I understand from your comment that I can ignore the errors when the site is visited by a visitor using something similar to uBlcok Origin, is that correct?
Yes, that is correct. When viewed without the ad blocker everything seems to be displaying properly.
-
This reply was modified 4 years, 3 months ago by
Bruce (a11n).
Thank you all.
Cemal
-
This reply was modified 4 years, 3 months ago by
The topic ‘Activating Jetpack creates error message in the console’ is closed to new replies.