Hi @waimanalo,
I’m sorry to hear about the trouble, but thanks for reaching out.
I can’t see the error code you mentioned, probably it got missed while you were sending the message here. Can you please paste it again for me?
Also, I’d like to dig deeper by checking your site directly. Could you post your site URL here, so I can have a look?
If you want it to remain private, you can also contact us via this contact form:
Contact Support. Thanks!
Hi Stef
Oops, sorry, had started the message last night and this morning, after checking if WP’s upgrade changed anything, forgot to paste the code, which I had retrieved **before** testing the plug ins and identifying jetpack. Code below.
The site is in development, so not visible online. I want to get everything done and working before going live, so I’m afraid you can’t see it 🙁
Just know I have run all the possible checks to see what could cause this — no plug in conflicts, site health check is fine, the only thing that triggers the problem is activating the jetpack plugin. That it worked for a month to suddenly go buggy (no additional plugins installed, was just working on content) is quite strange.
Thanks for your help
TypeError: Cannot read properties of undefined (reading '_mi_skip_tracking')
at render (https://humain-canin.fr/wp-content/plugins/google-analytics-for-wordpress/assets/gutenberg/js/editor.min.js?ver=8.3.1:6:74547)
at we (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:84:293)
at zj (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:226:496)
at Th (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:152:223)
at tj (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:152:152)
at Te (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:146:151)
at Ja (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:224:381)
at md (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:173:43)
at https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:175:222
at Rh (https://c0.wp.com/c/5.8.3/wp-includes/js/dist/vendor/react-dom.min.js:147:64)
Hello,
Just to be clear – Are you actually seeing this error populate onto the site or inside your post/page editor, or is it just a warning within a debugger or browser inspector that doesn’t cause any visual issues?
Hi
I get the “editor encountered an unexpected error” window within the widgets editor window (and that is the code that appears when you click the show error button.) I have not seen it crop up elsewhere (that I know of to date). It goes away when I deactivate Jetpack.
The site is in development and not visible to others on the Net.
Hi @waimanalo,
The plugin referenced in that error you shared is google-analytics-for-wordpress which appears to be making calls for some value in core wp-includes js files and getting a TypeError in the process which gets propagated to the editor screen.
TypeError represents a JavaScript error when an operation could not be performed, usually when a value is not of the expected type.
You may notice that the js files are being called from https://c0.wp.com/ which is an indicator that you’re using our CDN service to cache static files (like CSS and JavaScript) on your site.
If that’s happening whenever you activate Jetpack, it may be because something is not right with the way we’re minifying and compressing those files.
For us to confirm, can you please turn off Site Accelerator (particularly the option that says “Speed up static file load times”? There’s information about how to do that on our documentation.
Let us know if the error goes away after doing that.
Hi,
Yes, the error vanished after deactivating site acceleration. But why would the problem **suddenly** crop up?
Is there a fix?
Because site speed and image loading times are always issues and I prefer a “clean” WP with just the plugins I need, not a whole bunch of assorted ones (that’s a recipe for conflicts down the pike^)
It would be a shame to have to install another plugin because a feature in Jetpack is triggering bugs out the blue.
Thanks for your help 🙂
Hello @waimanalo
Please contact us via this contact form, so we can forward your issue to the Developers team to review it.
Please include a link to this thread in your message and your site URL.
Let me know if you have any questions.
My best regards,
Michelle
Hi Michelle
I’m afraid that’s a problem for 2 reasons:
1. I don’t have a wordpress.com account and do not wish to create an account which forces me to link my domain to it.
2. My website is not live yet, I am striving to debug a few issues before having it go online.
I should think either there is a direct email I can contact your developpers on or the information on this thread is sufficient to figure out what’s going on. It’s clear that activating the site acceleration feature is what triggers the bug in the widget’s editor..
Thanks 🙂
Hi @waimanalo
I’ve seen you’ve mentioned your site not being live yet and that you don’t have a WordPress.com account yet, so I’d suppose Jetpack is still not connected at all on your site; which is a requirement for the Site Accelerator feature to work properly as outlined in our guide:
https://jetpack.com/support/site-accelerator/
If the issue persists after the website is live and Jetpack is fully connected, we’d be happy to take a closer look.
Best,
The site is connected — I’d send you a screen shot, but can’t attach it here.
The site should be going live in a day or so, I’ll revert back.
Hey @waimanalo,
You can share screenshots if that helps. You can create screenshots using something like Snipboard or Imgur and post the link here.
Let us know how it goes when you site is live 🙂
Hi
Well, I’m stumped.
I’ve not even updated Jetpack and this morning, after reactivating site acceleration to show you what happens, the problem has disappeared as suddenly as it had appeared, again without any other element or change as a possible explanation…
Hi @waimanalo
Looks like there was something happening on your server’s end and it was fixed.
Let us know if you still have issues.
My regards,
Michelle
Anonymous User 18700194
(@anonymized-18700194)
Hi there,
It has been more than one week since we have heard from you, so I’m marking this topic as resolved.
But if you have any further questions or need some more help, you’re welcome to reply here or open another thread.
