2.0.2 breaks editor! “The editor has encountered an unexpected error.”

So sorry to hear you’re having issues with the 2.0.2 update.

Are you able to provide any additional information about the error, or the circumstances of the error?

• Are there any javascript errors in the console?
• Is this true for all posts and pages or only specific ones?
• Do you find using certain blocks breaks the editor, or is the editor broken immediately when trying to load a post?
• What version of WordPress is running on your website?
• What other plugins are running on the website? And have you tried deactivating other plugins to determine if the issue is the result of conflict?
• Do you have access to the PHP debug logs, and do they show any errors?

Anything you can provide about the website or the circumstances of the error would be helpful.

Thanks!

• This reply was modified 5 years, 1 month ago by jomurgel.

We updated our test server to 2.0.2 this morning and are seeing the same exact problem as @djosephdesign. Copy Error yields this:

parse@[native code]
value@https://[our-test-server].com/wp-content/plugins/publish-to-apple-news/build/pluginSidebar.js:1:32834
ce@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:98:142
Qg@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:144:219
Rg@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:145:78
Sc@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:158:111
Kc@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:155:18
ya@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:153:161
bh@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:160:257
https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:215:412
https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:164:142
$g@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:159:72
Wc@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:164:71
ao@https://[our-test-server].com/wp-includes/js/dist/edit-post.min.js:12:76423
ao@[native code]
value@https://[our-test-server].com/wp-includes/js/dist/editor.min.js:17:60961
value@[native code]
sh@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:164:415
rh@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:13:434
uh@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:13:488
Ge@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:15:160
vh@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:165:252
ad@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:15:447
cd@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:17:18
Uh@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:39:337
Zg@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:158:507
Xe@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:23:324
oc@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:40:306
unstable_runWithPriority@https://[our-test-server].com/wp-includes/js/dist/vendor/react.min.js:27:37
ah@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:159:178
xf@https://[our-test-server].com/wp-includes/js/dist/vendor/react-dom.min.js:40:47
xf@[native code]

Same issue. deactivated and the page editor loaded normally.

Same issue here! I had to deactivate this plugin to restore the ability to edit with the Block Editor.

Another fix is to install the Classic Editor, but at this time, deactivating this plugin is a better fix. Please update when you’ve fixed the issue.

We’re on WP 5.2.3 + use Tipi Builder for our archive pages, but the block editor for our posts/pages.

Hi all —

We’re working on a fix for this on a priority basis. It should be released tomorrow.

Thank you Kevin. Looking forward to the fix.

I just released v2.0.3. Please let me know if the new version fixes the issues you are experiencing, or if you have any problems with the new version.

Thanks!

Thanks, @kevinfodness. I just tried it here and I get the same error, unfortunately.

Rats. Is there any additional info in the error message? Also, can you verify your operating system and browser that you are using?

Ok, so… “time heals all wounds” — I can’t seen to get the error to re-appear now.

I’ll do more testing, of course, but… yeah, it seems fixed. Sorry about the false alarm!

• This reply was modified 5 years, 1 month ago by macgeekgab.

Awesome! Hopefully your browser just had the previous version of the JavaScript file cached, and it’s got the new one now. I’m going to close this issue, but if you have any trouble with 2.0.3, please let us know. Thanks!

Ahh! That makes sense. Along those lines: any advice you’d offer, in general, about what to do (and what to have all contributors do), after updating plugins like this to ensure a lingering issue doesn’t hold itself over?

We’re loading our assets using a cache-busting flag based on the new version of the plugin, so it *should* do this automatically, but in case it doesn’t you can hold down the shift key and click the reload button and your browser should grab a fresh copy of any cached files.

I can also confirm 2.0.3 resolved the problem.

Thank you!

Oops, I spoke too soon. This is _still_ broken. I even tried in an incognito window to ensure it wasn’t a caching issue.

I had mistakenly been editing a page and thus thought things were working. But when I went to edit a post, it was still broken. I’ll have to downgrade back to 2.0.1 or deactivate for now.