• Hello,

    I upgraded my wordpress dev website from 6.2.2 to 6.4.2 and I am facing an error when I open Post/Page Editor.

    TypeError: e.match is not a function
        at zr (/wp-includes/js/dist/block-editor.min.js?ver=f0bb1e364b792257eb17:26:98527)
        at save (/wp-includes/js/dist/block-library.min.js?ver=875919a30abea6016ef8:14:589864)
        at zr (/wp-includes/js/dist/blocks.min.js?ver=7204d43123223474471a:10:4798)
        at Ir (/wp-includes/js/dist/blocks.min.js?ver=7204d43123223474471a:10:5179)
        at /wp-includes/js/dist/blocks.min.js?ver=7204d43123223474471a:10:34027
        at Yn (/wp-includes/js/dist/blocks.min.js?ver=7204d43123223474471a:10:34143)
        at /wp-includes/js/dist/blocks.min.js?ver=7204d43123223474471a:10:35228
        at Zn (/wp-includes/js/dist/blocks.min.js?ver=7204d43123223474471a:10:35292)
        at /wp-includes/js/dist/blocks.min.js?ver=7204d43123223474471a:10:35030
        at Array.map (<anonymous>)

    The website loads fine, I did not find any errors on the Published Post/Pages.

    I have tried to disable plugins but still the error persists.
    Please let me know if you have any solution for this.
    Thanks & Regards.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @yashsharmats1,


    It seems like you’re encountering a JavaScript error in the WordPress Block Editor after upgrading your WordPress version.

    Here are some steps you can take to troubleshoot and potentially resolve the issue:

    1. Clear your browser cache and try accessing the Post/Page Editor again. Sometimes, cached JavaScript files can cause compatibility issues.
    2. Switch to a default WordPress theme (like Twenty Twenty-Three) to see if the issue persists. If the error disappears with a default theme, there might be a compatibility issue with your current theme.
    3. Ensure that all your plugins and themes are updated to their latest versions, as they may not be fully compatible with the new WordPress version.
    4. While you mentioned disabling plugins, try deactivating all plugins and then reactivating them one by one to identify if a specific plugin is causing the issue.

      All the best!
    Thread Starter yashsharmats1

    (@yashsharmats1)

    Hey Niko,

    Thanks for your response. by disabling plugins I had meant that I deactivated them but I haven’t tried to switch the themes and check the block editor. I will try that and will update here.

    Thread Starter yashsharmats1

    (@yashsharmats1)

    So After switching to twenty two theme, The editor loads up without any errors. So that makes the custom theme the sole reason for this error.
    Though the error stack refers a file in wp-includes instead of the theme. Any idea how I can pinpoint the exact breaking code inside the theme?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘e.match is not a function’ is closed to new replies.