• Hello.

    Currently in my environment, when I select Block Editor in Edit Page, I get “エディターで予期せぬエラーが発生しました(An unexpected error occurred in the editor)”.

    Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Oc (react-dom.min.js?ver=16.13.1:169:18)
    at react-dom.min.js?ver=16.13.1:80:357
    at T (react-dom.min.js?ver=16.13.1:95:457)
    at zj (react-dom.min.js?ver=16.13.1:227:428)
    at Th (react-dom.min.js?ver=16.13.1:152:223)
    at tj (react-dom.min.js?ver=16.13.1:152:152)
    at Te (react-dom.min.js?ver=16.13.1:146:151)
    at react-dom.min.js?ver=16.13.1:61:68
    at unstable_runWithPriority (react.min.js?ver=16.13.1:25:260)
    at Da (react-dom.min.js?ver=16.13.1:60:280)

    This error seems to be the same event as the following topic.
    https://www.ads-software.com/support/topic/aio-seo-breaks-gutenberg/

    I have several sites that I operate and some of them were resolved using aioseo_disable_link_format, but some remained in error.
    My company is currently having a little difficulty updating to the latest WordPress version.

    WordPress:5.8.10
    AIO SEO:4.7.3

    My WordPress environment is as follows.

    Please confirm.

Viewing 1 replies (of 1 total)
  • Thread Starter nhayashi

    (@nhayashi)

    While investigating, it seems that there may be a conflict with the plugin “Search Exclude”.

    It appears that custom-sidebar-metabox cannot be rendered with AIO SEO and Search Exclude in place.
    (I have confirmed that the AIO SEO / Search Exclude plugin by itself does not cause an error, but two of them do.)

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.