• I have updated WordPress to 5.4 version on the front side everything works great but admin panel there are some issues occurred, when I’m on the editing page it fires errors in the developer console like m.find is not a function, probably error in react-dom.js file or something also sometimes it fires error from edit.php file, I don’t understand what a hell is going on maybe some plugin causes it maybe other thing, moreover older posts have issue inner blocks have been broken and saying that “This block contain error and can’t be displayed”, Why this happened I have just made a single step from 0.3 to 0.4 and too many bugs, I though that maintenance between those versions would be kept but no. Can someone help me with this pitfall?

    TypeError: m.find is not a function
    at block-editor.min.js?ver=704b9a6d689b18b6982a8b2ae902e7ec:50
    at Array.reduce (<anonymous>)
    at block-editor.min.js?ver=704b9a6d689b18b6982a8b2ae902e7ec:50
    at Object.useMemo (react-dom.min.js?ver=16.9.0:205)
    at useMemo (react.min.js?ver=16.9.0:32)
    at Me (block-editor.min.js?ver=704b9a6d689b18b6982a8b2ae902e7ec:50)
    at Rt (block-library.min.js?ver=f710d3cc99e7a55a0d6a5418f3cfe33c:9)
    at je (react-dom.min.js?ver=16.9.0:78)
    at ph (react-dom.min.js?ver=16.9.0:215)
    at lh (react-dom.min.js?ver=16.9.0:126)`
    GET https://example/wp-content/plugins/xs-wp-post-hide/assets/js/xswpph-script.js?ver=5.4 net::ERR_ABORTED 404 (Not Found)

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    The error seems to be coming from a plugin, WP Post Hide. Try disabling it. If you can’t do that from the dashboard, rename wp-content/plugins/wp-post-hide to something like wp-content/plugins/wp-post-hide-xyz. Use FTP or the file manager app of your hosting control panel.

    I also recommend asking at https://wordpress.org/support/plugin/wp-post-hide/#new-post so the plugin’s developers and support community can help you with this.

    Thread Starter e110

    (@e110)

    Tried but still react and tinymce errors are exist.. What may cause that issue? And as I said before the blocks which I have built using gutenberg are not visible it displayed as errors, Was it predictable due the upgrade or its error?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Two things:

    1. This may be a plugin or theme conflict. Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.

    If you can install plugins, install “Health Check”: https://wordpress.org/plugins/health-check/ On the troubleshooting tab, you can click the button to disable all plugins and change the theme for JUST you, while you’re still logged in, without affecting normal visitors to your site. You can then use its admin bar menu to turn on/off plugins and themes one at a time. See https://make.wordpress.org/support/handbook/appendix/troubleshooting-using-the-health-check/ for more information.

    2. If that doesn’t provide a clue as to what’s happening, please use the info tab from health check to copy/paste a status report back here (and please include info on what browser you’re using, too).

    Thread Starter e110

    (@e110)

    Yes, Hello I have found that changing theme to wordpress initial theme solves the blocks appearance problem it displays! But anyways doesn’t work on my current theme. How can I fix this problem, the theme is no longer supported, Is there any general changes that may be solve that problem? I mean I didn’t find anything to find out migrate options, and still how did it happen while issue is only in admins edit page.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    >> How can I fix this problem, the theme is no longer supported <<

    You could hire a developer to fix the theme or find another one.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Errors occurred after WordPress 5.4 upgrade’ is closed to new replies.