Jetpack causing “editor has encountered an unexpected error”

Hello @reeyleow,

I can’t get your site URL from the errors you shared.

Can you tell me more about that? I’d like to replicate this on my end, so the more information you can share, the better! You can share screenshots if that helps. You can create screenshots using something like Snipboard or Imgur and post the link here.

Another thing you can do, provided you reconnect Jetpack, is to temporarily deactivate all your plugins and check if the problem gets fixed that way. If it works, then reactivate each plugin one by one to find out which one is causing problems.

If it’s not a plugin conflict, it could be a theme one. Can you try to temporarily switch your theme to Twenty Twenty and see if the problem persists?

Also, it’d be useful to see your site: could you post your site URL here so that we can have a look? If you want it to remain private, you can also contact us via contact form. If you choose to reach out directly, please include a link to this thread.

Let me know what you find out!

@erania-pinnera

Hi! Thanks for getting back to me. Here is a link with a gallery where I recreated a similar issue. Screenshots are included in the linked post below the gallery that triggered the issue

https://touchingdoodles.com/jetpack-issue-test/

Since the latest jetpack update the issue has changed slightly. Now when first creating a new gallery I don’t get an error. However when I try to add additional images to a gallery the same editor error occurs. This is what I’ve shown via the screen captures in my post.

I originally tracked down jetpack as the cause of the issue after deactivating all my plugins and working through which one created the error.

I’m using a child theme built on Twenty Twenty Two

Hi there, @reeyleow,

Thanks for recreating the problem in that gallery (fantastic drawings by the way! The octopus would definitely fit as a tattoo on my arm ?? )

I suspect the issue is being triggered by the Gutenberg plugin. What happens if you turn it off completely?

Hi @erania-pinnera

When I originally got the error I hadn’t yet downloaded Gutenberg. So after deactivating Gutenberg the error returns to how it was before – the error pops up when creating the gallery. After deactivating jetpack I’m able to create a gallery as per normal. I’ve added screenshots and the error code for this test to the same post.

And thanks for the nice words about my art! I have a “please get that tattoo and let me know” policy!

Hi @reeyleow,

Hmm the plot thickens. I see the screenshot with the The editor has encountered an unexpected error.

If you copy/paste the error (by clicking on the “Copy Error” button, do you get the same errors you already mentioned? Do you see differences in this error whether the Gutenberg plugin is enabled or not?

Also, you said to be on a child theme. Does the issue persist if you test it on a default theme?

****

I have a “please get that tattoo and let me know” policy!

That’s really interesting! I will contact you privately at some point ??

Hello, I am having the exact same issue and do not have the Gutenberg plugin installed, so I don’t believe that’s the problem. I do however have the Jetpack plugin (Version 13.1.3) installed and activated. My site uses the Inspiro theme by WPZOOM.

Hi there, @jbrunetti,

That’s interesting. Do you mind opening your own thread as per the Forum Welcome?
Here’s the link: https://www.ads-software.com/support/plugin/jetpack#new-post
?
When doing it, could you also try to temporarily switch your theme to Twenty Twenty and see if the problem persists?

If so, please share a screenshot of the errors you see, or paste it in your post. Thanks!

Hi @erania-pinnera,

The errors with/without the Gutenberg plugin have one section in common. These are the ending lines of the Copy Error text for both scenarios:
…
p@https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:3704 @https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:3498 a@https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:693 @https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:3381 _onModelEvent@https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:14087 p@https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:3762 @https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:3509 a@https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:693 @https://c0.wp.com/c/6.4.3/wp-includes/js/backbone.min.js:2:3381 click@https://c0.wp.com/c/6.4.3/wp-includes/js/media-views.min.js:2:71225 click@https://c0.wp.com/c/6.4.3/wp-includes/js/media-views.min.js:2:50906 dispatch@https://c0.wp.com/c/6.4.3/wp-includes/js/jquery/jquery.min.js:2:40040

The top section of the error without Gutenberg

mI@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/block-editor.min.js:41:75917 wt@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:47638 vr@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:56454 wl@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:88661 bl@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:88589 yl@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:88452 il@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:85276 fl@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:85663 Nn@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:32475 al@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:82723 Rt@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:50493 @https://c0.wp.com/c/6.4.3/wp-includes/js/dist/vendor/react-dom.min.js:10:50352 s@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/data.min.js:9:2081 u@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/data.min.js:9:2107 @https://c0.wp.com/c/6.4.3/wp-includes/js/dist/data.min.js:2:21102 @https://c0.wp.com/c/6.4.3/wp-includes/js/dist/data.min.js:2:20062 p@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/data.min.js:2:9322 @https://c0.wp.com/c/6.4.3/wp-includes/js/dist/data.min.js:2:17637 A@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/block-library.min.js:14:123271 onUpdate@https://c0.wp.com/c/6.4.3/wp-includes/js/dist/media-utils.min.js:2:4663

Bottom section of the error WITH Gutenberg

PT@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/block-editor/index.min.js:157:9218 St@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:47628 yr@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:56444 Sl@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:88651 kl@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:88579 bl@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:88442 sl@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:85266 dl@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:85653 Nn@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:32465 ul@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:82713 Dt@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:50483 @https://touchingdoodles.com/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js:1:50342 s@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/data/index.min.js:1:24598 c@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/data/index.min.js:1:24624 @https://touchingdoodles.com/wp-content/plugins/gutenberg/build/data/index.min.js:1:20359 @https://touchingdoodles.com/wp-content/plugins/gutenberg/build/data/index.min.js:1:18687 b@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/data/index.min.js:1:8078 @https://touchingdoodles.com/wp-content/plugins/gutenberg/build/data/index.min.js:1:16092 z@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/block-library/index.min.js:32:46586 I@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/block-editor/index.min.js:11:6071 onUpdate@https://touchingdoodles.com/wp-content/plugins/gutenberg/build/media-utils/index.min.js:1:4196

It looks like @jbrunetti‘s error message has the same bottom section as both my examples (based on their post) The editor has encountered an unexpected error. | www.ads-software.com

Hi there, @reeyleow,

I did more research, and it seems like the TypeError you reported reflects a JavaScript error triggered when an operation could not be performed, usually when a value is not of the expected type.

I noticed that the js files are being called from?https://c0.wp.com/,?which shows that our CDN service in enable and is caching static files (like CSS and JavaScript) on your site.

This means that something might not right with the way we’re minifying and compressing those files.

To check on my suspicions, can you please turn off Site Accelerator (specifically the “Speed up static file load times” option) to see if that helps fix the issue? There is information about how to do that in?our documentation.

Let me know how you get on.

Hi @erania-pinnera,

I tried turning off both site accelerator options as per your link and I continue to get an unexpected editor error problem. Error code below

mI@https://touchingdoodles.com/wp-includes/js/dist/block-editor.min.js:41:75917
wt@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:47638
vr@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:56454
wl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:88661
bl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:88589
yl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:88452
il@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:85276
fl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:85663
Nn@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:32475
al@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:82723
Rt@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:50493
@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:50352
s@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:9:2081
u@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:9:2107
@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:21102
@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:20062
p@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:9322
@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:17637
A@https://touchingdoodles.com/wp-includes/js/dist/block-library.min.js:14:123271
onUpdate@https://touchingdoodles.com/wp-includes/js/dist/media-utils.min.js:2:4663
p@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3704
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3498
a@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:693
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3381
_onModelEvent@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:14087
p@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3762
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3509
a@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:693
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3381
click@https://touchingdoodles.com/wp-includes/js/media-views.min.js:2:71225
click@https://touchingdoodles.com/wp-includes/js/media-views.min.js:2:50906
dispatch@https://touchingdoodles.com/wp-includes/js/jquery/jquery.min.js:2:40040

Hi @reeyleow

I ran some further tests on your site, and it seems that although your domain has a valid SSL certificate, it is still possible to access your site via HTTP. Your visitors and search engines can use either HTTP or HTTPS to access your site. It can also be accessed either with or without the www in front of the domain.

This is an issue for search engines, since it often causes confusion and duplicate content, but it is also an issue for your site’s communication with Jetpack, as our system does not know whether it should connect to your site via one or the other address.

To solve this issue, I would recommend that you change your site’s URL to HTTPS (you can do so under Settings > General in your dashboard), and then ask your host for help redirecting all traffic from HTTP to HTTPS.

If your host is unable to help with that, you can follow the instructions here to do so:

https://www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress/

Once that’s done, try to reconnect your site to Jetpack once again and see if that helps.

<span data-slate-node=”text”><span data-slate-leaf=”true”><span data-slate-string=”true”></span></span></span>

Hi @bruceallen,

Thanks for the suggestion re: my SSL setup. I’ve gone and fixed it up so http is forced to redirect to https. After disconnecting and reconnecting jetpack but I’m continuing to have what seems like the same issue. Error code is copied below.

mI@https://touchingdoodles.com/wp-includes/js/dist/block-editor.min.js:41:75917
wt@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:47638
vr@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:56454
wl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:88661
bl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:88589
yl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:88452
il@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:85276
fl@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:85663
Nn@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:32475
al@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:82723
Rt@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:50493
@https://touchingdoodles.com/wp-includes/js/dist/vendor/react-dom.min.js:10:50352
s@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:9:2081
u@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:9:2107
@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:21102
@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:20062
p@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:9322
@https://touchingdoodles.com/wp-includes/js/dist/data.min.js:2:17637
A@https://touchingdoodles.com/wp-includes/js/dist/block-library.min.js:14:123271
onUpdate@https://touchingdoodles.com/wp-includes/js/dist/media-utils.min.js:2:4663
p@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3704
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3498
a@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:693
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3381
_onModelEvent@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:14087
p@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3762
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3509
a@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:693
@https://touchingdoodles.com/wp-includes/js/backbone.min.js:2:3381
click@https://touchingdoodles.com/wp-includes/js/media-views.min.js:2:71225
click@https://touchingdoodles.com/wp-includes/js/media-views.min.js:2:50906
dispatch@https://touchingdoodles.com/wp-includes/js/jquery/jquery.min.js:2:40040

Hi there,

I tested the scenario you shared and couldn’t replicate the issue on my test site.

Could you confirm if the issue persists when Jetpack is the only active plugin and a default theme like Twenty Twenty-One is active?

It would also be helpful to know the current version of Jetpack you are using.

To assist you further, could you please post your site URL here so that we can have a look? If you want it to remain private, you can also contact us via?contact form. If you choose to reach out directly, please include a link to this thread.

Thank you!

Hi there,

I tested the scenario you shared on my site but couldn’t replicate the issue.

Could you confirm if the issue persists when Jetpack is the only active plugin and a default theme like Twenty Twenty-One is active?

It would also be helpful to know the current version of Jetpack you are using.

To assist you further, could you please post your site URL here so that we can have a look? If you want it to remain private, you can also contact us via?contact form.?If you choose to reach out directly, please include a link to this thread.

Thank you!