“This block has encountered an error and cannot be previewed” after update 6.5

  • Resolved wpzugang

    (@wpzugang)


    6 months, 2 weeks ago

    After updating to wordpress 6.5 with theme Twenty-Twenty-Three, I cannot read the text blocks anymore after I click on “Edit template” 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. Same problem with 6.5.3 still not solved.

    I deactivated all plugins but the problem still appears.

    https://bluwing.de/wp-content/uploads/block-errort.jpg

    Any ideas?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter wpzugang

    (@wpzugang)

    Are there still any compatibility checks with this theme and wordpress? Would like to update my websites but is quite uncofortable to downgrad to 6.4.3 every time when I want to make a change on my websites.

    Thread Starter wpzugang

    (@wpzugang)

    These are the error messages I get from the console. Don’t know if this has anything to do with my problem or how to get rid of these error messages:

    WebExtension context not found! 3 ExtensionParent.sys.mjs:1278:13

????getContextById resource://gre/modules/ExtensionParent.sys.mjs:1278

????recvRemoveListener resource://gre/modules/ExtensionParent.sys.mjs:1257

????_recv resource://gre/modules/ConduitsChild.sys.mjs:77

????receiveMessage resource://gre/modules/ConduitsParent.sys.mjs:469

AbortError: Actor 'Conduits' destroyed before query 'RuntimeMessage' was resolved ConduitsParent.sys.mjs:378

????_raceResponses resource://gre/modules/ConduitsParent.sys.mjs:378
this.window.gBrowserInit is undefined ext-browser.js:1114:9

????get activeTab chrome://browser/content/parent/ext-browser.js:1114

????candidates chrome://extensions/content/parent/ext-tabs-base.js:2105

????next self-hosted:1386

????query chrome://extensions/content/parent/ext-tabs-base.js:2127

????next self-hosted:1386

????from self-hosted:579

????query chrome://browser/content/parent/ext-tabs.js:1006

????result resource://gre/modules/ExtensionParent.sys.mjs:1137

????withCallContextData resource://gre/modules/ExtensionParent.sys.mjs:611

????result resource://gre/modules/ExtensionParent.sys.mjs:1136

????withPendingBrowser resource://gre/modules/ExtensionParent.sys.mjs:621

????result resource://gre/modules/ExtensionParent.sys.mjs:1135

????callAndLog resource://gre/modules/ExtensionParent.sys.mjs:1086

????recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1134

????AsyncFunctionNext self-hosted:852
    Thread Starter wpzugang

    (@wpzugang)

    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.

    I don’t have this extension, and tried to edit the pages in Chrome. Firefox and Edge with no success.

    All my Back-end pages turned into an identical ‘This block has encountered an error and cannot be previewed’ mess after WordPress Core update to 6.5.3

    Thread Starter wpzugang

    (@wpzugang)

    @ivanpr Since this forum is quiet dead (don’t know why), I would suggest that you open a new issue at GitHub. There I immidiately got help:

    https://github.com/WordPress/gutenberg/issues/61632

    Let me know if you had success.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘“This block has encountered an error and cannot be previewed” after update 6.5’ is closed to new replies.