Latest update, The editor has encountered an unexpected error.

  • akiraanastasia

    (@akiraanastasia)


    2 years ago

    After updating to latest WordPress 6.1 I am getting error while adding new post, page or edit existing posts. Error:
    The editor has encountered an unexpected error.

    There are 3 buttons: Last one is Copy Error. So here is Copied Error:

    TypeError: (0 , ko.isAppleOS) is not a function
    at https://example.com/wp-includes/js/dist/editor.min.js:12:51498
    at ct (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:43430)
    at It (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:48875)
    at os (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:113180)
    at Ur (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:77643)
    at Ir (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:77571)
    at Dr (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:77434)
    at Pr (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:74429)
    at https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:30173
    at unstable_runWithPriority (https://example.com/wp-includes/js/dist/vendor/react.min.js:9:7431)

    SOMEONE PLEASE HELP ME!!

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Please do not create duplicate topics. I have archived your two new ones.

    Thread Starter akiraanastasia

    (@akiraanastasia)

    @jdembowski Ok, i thought those topics were on different plugins so they are considered as different. Will not happen again.
    How we will know if this error is causing due to this page’s plugin or different one. That’s why I posted on another plugin’s support page too. I am unable to create new post.

    CGS Web Designs

    (@cgscomputers)

    I had this exact same issue on one of my sites after upgrading to WP 6.1. I am not sure exactly what fixed it, but here’s what I did…

    I used the Health Check & Troubleshooting plugin to enable troubleshooting mode. I was then able to use the editor (with all plugins disabled in troubleshooting mode). I then disabled troubleshooting mode and cleared my browser cache. I was then able to access the editor.

    The quickest way to clear your browser cache is to hit F12 which opens the developer console, then right-click the reload button in the browser and choose “clear cache and hard reload” from the context menu. Also try using a fresh browser in incognito/private mode.

    janiosarmento

    (@janiosarmento)

    I had the same problem. My functional workaround was installing the “Gutenberg” plugin. So far, so good.

    joaomfmartins

    (@joaomfmartins)

    @akiraanastasia Did you fixed this issue?

    I’m having the same issue when I open the page editor. Besides that my website is deconfigured and unformatted. It seems like the css is not being applied to the website.

    @janiosarmento I tried your approach and installed the “Gutenberg” plugin. The truth is that I can now open the editor, but the website continues “without css”…

    Any idea?

    Wordpress version: 6.1
    Elementor version: 3.8.0
    Blocksy theme version: 1.8.55
    Blocksy companion version: 1.8.55

    janiosarmento

    (@janiosarmento)

    It’s most likely due to an older version of Elementor (I hate this plugin). But it’s a shot in the dark because no idea can be made without first inspecting the errors in the browser console.

    joaomfmartins

    (@joaomfmartins)

    Okay, I will have a look. That’s interesting because I’ve been using elementor for a long time. This is the first time it happens to me. Did you experience more errors like this related to elementor?

    janiosarmento

    (@janiosarmento)

    Oh, absolutely, I’ve had enough of Elementor-related troubles. However, they were all resolved with an update (there are clients who do not update their paid plugins, unless they suffer some external pressure to do it).

    Thread Starter akiraanastasia

    (@akiraanastasia)

    @joaomfmartins Clearing browser cache solved this issue. But I also waited next 10-12 hours before login. Hope you are able to add new posts now.

    lukascech

    (@lukascech)

    @cgscomputers – your clearing cache suggestion fixed it for me, thanks! It fixed it straight away for me, no waiting (have also manually deleted all cookies, in the developer console > cookies > select your website > keep pressing delete until all is clear.

    wrip

    (@wrip)

    I had the same issue on my localhost site but when I logged into the website using Private mode, everything worked normally. So, must be a browser cache issue.

    joaomfmartins

    (@joaomfmartins)

    My server uses Varnish HTTP Cache and that was causing the issue. I turned off this caching mechanism and it is working now.

    This issue appears to be because The request made to react-dom.min.js has the version number appended of 17.0.1:

    react-dom.min.js?version=17.0.1

    However the file version required is 17.0.2. Any caching such as Varnish would not return the correct file due the cached request

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Latest update, The editor has encountered an unexpected error.’ is closed to new replies.