Viewing 5 replies - 1 through 5 (of 5 total)
  • Hello @ocsaroy

    What block are you editing when you get the error? Do you have a screenshot of the list view of the block you’re trying to edit? Unfortunately, the stack trace you provided isn’t enough to determine what is happening.

    The same thing happens to me, when I go to the widget arrangement

    Hello @vietlongtravel

    Do you have screenshots of the error when it occurs? Does it happen when you move widgets, or when you immediately visit the widget editor? Unfortunately, I can not reproduce the problem without more information.

    Thread Starter ocsaroy

    (@ocsaroy)

    @ghernkadence , hello

    Here is the video that shows the error.
    https://drive.google.com/file/d/1fBAjTBG3MimFhE-fLr_XHeSzYpHfnZI_/view?usp=sharing
    My website on Ubuntu VPS with VESTACP that uses PHP8

    It happens when I visit elements in editor.

    • This reply was modified 2 years, 8 months ago by ocsaroy.
    • This reply was modified 2 years, 8 months ago by ocsaroy.

    Hello @ocsaroy and @vietlongtravel

    I see the video provided by a previous post. The video shows an error I often come across when using frontend translation from Google. I mention this because the video shows the admin uses English, but the content of the page is a foreign language.

    As a support agent, I often visit sites that are in different languages. In these cases, my browser extension asks me if I want to preserve the site language or translate the page. Personally, I experience the same page break when the language is not English, my browser extension translates the content of the page, and I select content within the Gutenberg list view in the same way the video shows. When I view foreign languages in Gutenberg, I cannot use the browser extension to translate Gutenberg content because the page breaks.

    Is it possible you are experiencing the same problem I described? If so, could you disable the frontend translation and see if that solves the problem?

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

The topic ‘Error: Failed to execute ‘removeChild’ on ‘Node’’ is closed to new replies.