Conflict with Classic Editor

  • Resolved Sonya

    (@sonyalou)


    3 years, 10 months ago

    Hi all!

    We have the following error code on our website. We have the Classic Editor, Advanced Editor Tools (previously TinyMCE Advanced) and someone suggested there could be a conflict with Yoast SEO.

    I’m not sure what to think as we have been using all these plugins for some time now. This has been an issue this past few weeks on both posts and pages when editing or creating a new page or post and we are unable to use the editing options that we used previously. … and believe this is impacting our use of the editor with regard to functionality (ie the editor toolbar is missing functions such as insert link, read more, horizontal line, bullet points etc)

    Thanks in advance!`

    Uncaught Error: Minified React error #200; visit https://reactjs.org/docs/error-decoder.html?invariant=200 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at I.render (react-dom.min.js?ver=16.13.1:238)
    at t.renderClassicEditorMetabox (classic-editor-1611.js:1)
    at Object.t.default [as initEditorIntegration] (classic-editor-1611.js:1)
    at HTMLDocument.<anonymous> (post-edit-1611.js:1)

    • This topic was modified 3 years, 10 months ago by Sonya.
Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi @sonyalou ,

    We are sorry to hear about the error you are getting. Let’s see what’s going on. Just to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

    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.

    As we can imagine that 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.

    If you do not feel comfortable to do this yourself or if this does not solve your issue, our Yoast SEO Premium plugin comes with one year of (technical) support.

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with Classic Editor’ is closed to new replies.