Serious block editor issue: This block has encountered an error and cannot be…

  • generare

    (@generare)


    1 year ago

    Hello, our website has been unusable since the update on the August 2023. We are using very simple setup, having unedited core and twentytwentytwo in usage. The block editor hasn’t been working since August and we had to make edits via code view and that means that only one skilled person can update it and very slowly compared that the block editor would work.

    When ever you click the block editor content it says:

    “This block has encountered an error and cannot be previewed.”

    If I put the debugging on, it says:

    “Notice: Undefined index: slug in /home/xxxuyyy/public_html/fi/wp-includes/class-wp-theme-json.php on line 1685

    Notice: Undefined index: slug in /home/xxxuyyy/public_html/fi/wp-includes/class-wp-theme-json.php on line 1731″

    Those lines has matters about “slug” presets. If I change to twentytwentyone, there is no problems with the block editor but obviously the website doesn’t look at all what it should look like, so we can’t use that theme.

    We have also re-installed the Current version: 6.3.2 (en-GB) and we have deactivated temporarily the twentytwentytwo, deleted it and installed it again. Still the same block editor issue persists.

    We also lately realised that the mobile version is not working properly but that we can investigate only when we get the block editor issue solved. We do think that there is something wrong with the twentytwentytwo theme itself because we tried to avoid indeed theme issues by using WP’s own themes and making only visual content edits on it and thus be safe for updates and now we got this long and serious issue for this theme that appeared exactly after August automatic WP update.

    It would be great if we would find the issue causing the problems with the theme “twentytwentytwo”.

    • This topic was modified 1 year ago by generare. Reason: strange layout for the support question
    • This topic was modified 1 year ago by generare. Reason: Also this website block editor has some issues ;) sorry for the re-editing multiple times due to that
Viewing 13 replies - 1 through 13 (of 13 total)
  • Kavya Gokul

    (@properlypurple)

    Hey @generare! This sounds quite frustrating. Can you share a few more details about your setup, specifically:

    • Does this happen with certain type of blocks?
    • Do you have the Gutenberg plugin installed?
    • Do you have any other plugins installed which may provide additional blocks?
    Thread Starter generare

    (@generare)

    Hello,
    We are mainly using normal text blocks. It happens in every single page when editing any of these text blocks. Gutenberg plugin was installed but we first deactivated it and then also deleted. The problem persisted after that too.

    We have extremely simple setup in order to avoid this type of issues. We have only plugin “Redirection” and “Yoast SEO” installed. And we have also deactivated them in order to test if it would help but it didn’t.

    • This reply was modified 1 year ago by generare.
    Moderator jordesign

    (@jordesign)

    Hi @generare,

    “This block has encountered an error and cannot be previewed.”

    This error usually occurs when the code within a block doesn’t match the editor’s expectations of what the structure/code of a block should be…

    I see you also mentioned this…

    The block editor hasn’t been working since August and we had to make edits via code view and that means that only one skilled person can update it and very slowly compared that the block editor would work.

    Because of what I mentioned above – I suspect the errors are from the HTML of the blocks being edited manually. Can you tell me more about what wasn’t working about the editor in the first place?

    Thread Starter generare

    (@generare)

    The problem just appeared when the WP made the automatic August update. There is no special coding on it or HTML edits, just had been using the block editor to add content on it and there were no issues before August.

    If you inspect the element that gets the error “This block has encountered an error and cannot be previewed”, you get this:

    TypeError: undefined has no properties

????l https://www.mydomain.fi/fi/wp-includes/js/dist/block-editor.min.js?ver=6bf412b7afa6151863a3:26

????Qb https://www.mydomain.fi/fi/wp-includes/js/dist/block-editor.min.js?ver=6bf412b7afa6151863a3:26

????Yb https://www.mydomain.fi/fi/wp-includes/js/dist/block-editor.min.js?ver=6bf412b7afa6151863a3:26

????xv https://www.mydomain.fi/fi/wp-includes/js/dist/block-editor.min.js?ver=6bf412b7afa6151863a3:26

????wt https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????js https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????wl https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????bl https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????yl https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????il https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????fl https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????Nn https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10

????ul https://www.mydomain.fi/fi/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10
    Moderator jordesign

    (@jordesign)

    Hi @generare – another thing that would be really helpful to check… Could you please try activating another theme like TwentyTwentyThree – and seeing if you still have the errors on those blocks?

    Thread Starter generare

    (@generare)

    Hi, as I said in my original post:
    “If I change to twentytwentyone, there is no problems with the block editor but obviously the website doesn’t look at all what it should look like, so we can’t use that theme.”

    And I repeat, we have not made any changes, edits to twentytwentytwo, and I have re-installed it too. So, maybe somebody could repeat the issue using the standard twentytwentytwo and put some text and use the block editor?

    Moderator jordesign

    (@jordesign)

    Hi @generare,

    Would you be willing to share the HTML of one of the pages with errors in this thead? Then I can copy it into my own test site to try things out?

    Thread Starter generare

    (@generare)

    Since the error happens in the admin, do you mean the whole page source or what? Do I send it privately to you somehow? (I do not know if it is possible in this forum).

    Moderator jordesign

    (@jordesign)

    Hi @generare,

    If you go to edit the page – you can click the button with three dots at top right of the editor and select ‘Copy All Blocks’

    You can then paste it into a reply here in the forums so I can see it. If you use a Code block (by typing /code ) it will retain the code of the page.

    Having the same problem with all text blocks after updating to wordpress 6.5 with theme Twenty-Twenty-Three. Same with all my three wordpress websites . With a downgrade to 6.4.3 the problem dissappears. After updating to 6.5 again, the problem occours again.

    Just received the 6.5.2 update, still same problem. Only appears in the template editor.

    I have created a new topic that is related to my theme: https://www.ads-software.com/support/topic/this-block-has-encountered-an-error-and-cannot-be-previewed-after-update-6-5/

    With the help of the Gutenberg team, I found out that this problem is only caused by my browser extension NoScript . Really strange that it worked until WP 5.4.3, even with the addon activated.

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