Unexpected error in editor

  • Resolved mmwbadmin

    (@mmwbadmin)


    2 years, 6 months ago

    Hi,
    after updating to 19.6.1 on WP 6.0.2 editing posts/pages is no longer possible. Error message: editor encounters an unexpected problem (¨De editor is op een onverwacht probleem gestuit.”)

    I reinstalled 2 previous versions of Yoast, but issue remained. Disabling the plugin helps to use the editor again.

    PHP 8, Weaver Xtreme theme

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support devnihil

    (@devnihil)

    @mmwbadmin We’re sorry to hear you are experiencing this issue on your site.

    If you have already confirmed that both Yoast SEO and WordPress are up to date and the issue is still occurring, we would next recommend performing a conflict check to determine whether another plugin or theme is interfering with the Yoast plugin.

    The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?TwentyTwentyOne.

    Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

    If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

    Thread Starter mmwbadmin

    (@mmwbadmin)

    Hi,
    it seems that Yoast conflicts with my child theme of Weaver Xtreme all of a sudden. It works fine along with just the parent theme.
    Nothing changed in the child theme over the last year (probably longer)

    Thread Starter mmwbadmin

    (@mmwbadmin)

    More information on the error:

    TypeError: Cannot read properties of undefined (reading 'every')
    at ue (https://www.mmwb.nl/wp-content/plugins/wordpress-seo/js/dist/block-editor.js:462:12174)
    at ct (https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:43430)
    at os (https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:111136)
    at Ur (https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:77643)
    at Ir (https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:77571)
    at Dr (https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:77434)
    at Pr (https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:74429)
    at https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:30173
    at unstable_runWithPriority (https://www.mmwb.nl/wp-includes/js/dist/vendor/react.min.js:9:7431)
    at xn (https://www.mmwb.nl/wp-includes/js/dist/vendor/react-dom.min.js:9:29950)
    Thread Starter mmwbadmin

    (@mmwbadmin)

    @devnihil See also this issue with MapPress

    that points to this message

    Thread Starter mmwbadmin

    (@mmwbadmin)

    @devnihil and this recent issue with SEOPress

    having the exct same issue. I use a different theme (Workscout) so I don’t think this is theme-specific. 

    TypeError: Cannot read properties of undefined (reading 'every')
    at ue (https://example.com/wp-content/plugins/wordpress-seo/js/dist/block-editor.js:462:12174)
    at ct (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:43430)
    at os (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:111136)
    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)
    at xn (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js:9:29950)
    Thread Starter mmwbadmin

    (@mmwbadmin)

    Clearing browser cache (!) solved issue in my case
    @devnihil

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Unexpected error in editor’ is closed to new replies.