Barenco

I found this article that talks about the problem. What do you think?

https://codefaq.org/wordpress/how-to-fix-gutenberg-error-cannot-read-property-show_ui-of-undefined/

We are having the same problem. Since the last automatic update of WordPress, two days ago, the Block Editor stopped working, both for editing already published posts and for new posts. After opening for a few seconds, we get a blank screen with this same error message.

We are having the same problem. Since the last automatic update of WordPress, two days ago, the Block Editor stopped working, both for editing already published posts and for new posts. After opening for a few seconds, we get a blank screen with this same error message.

JQMIGRATE: Migrate is installed, version 3.3.2
admin.js?ver=1.3.2:1348 undefined undefined
googlesitekit-vendor-e20382a143485ba05084.js:7 TypeError: Cannot read properties of null (reading '0')
    at googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:21:777
    at e.exports (googlesitekit-vendor-e20382a143485ba05084.js:7:515150)
    at e.exports (googlesitekit-vendor-e20382a143485ba05084.js:7:865028)
    at v (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:21:740)
    at h (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:21:1107)
    at Overview (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:58:441)
    at Ih (googlesitekit-vendor-e20382a143485ba05084.js:7:678974)
    at wi (googlesitekit-vendor-e20382a143485ba05084.js:7:724065)
    at ga (googlesitekit-vendor-e20382a143485ba05084.js:7:709669)
    at Zj (googlesitekit-vendor-e20382a143485ba05084.js:7:709594)
Pi @ googlesitekit-vendor-e20382a143485ba05084.js:7
googlesitekit-module-85767e992b6ad9b5181b.js:21 Caught an error: TypeError: Cannot read properties of null (reading '0')
    at googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:21:777
    at e.exports (googlesitekit-vendor-e20382a143485ba05084.js:7:515150)
    at e.exports (googlesitekit-vendor-e20382a143485ba05084.js:7:865028)
    at v (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:21:740)
    at h (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:21:1107)
    at Overview (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:58:441)
    at Ih (googlesitekit-vendor-e20382a143485ba05084.js:7:678974)
    at wi (googlesitekit-vendor-e20382a143485ba05084.js:7:724065)
    at ga (googlesitekit-vendor-e20382a143485ba05084.js:7:709669)
    at Zj (googlesitekit-vendor-e20382a143485ba05084.js:7:709594) Object
value @ googlesitekit-module-85767e992b6ad9b5181b.js:21
googlesitekit-vendor-e20382a143485ba05084.js:7 TypeError: Cannot read properties of null (reading '0')
    at googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:17:1316
    at Array.forEach (<anonymous>)
    at p (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:17:1270)
    at Stats (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:58:2328)
    at Ih (googlesitekit-vendor-e20382a143485ba05084.js:7:678974)
    at wi (googlesitekit-vendor-e20382a143485ba05084.js:7:724065)
    at ga (googlesitekit-vendor-e20382a143485ba05084.js:7:709669)
    at Zj (googlesitekit-vendor-e20382a143485ba05084.js:7:709594)
    at Lj (googlesitekit-vendor-e20382a143485ba05084.js:7:706940)
    at googlesitekit-vendor-e20382a143485ba05084.js:7:665370
Pi @ googlesitekit-vendor-e20382a143485ba05084.js:7
googlesitekit-module-85767e992b6ad9b5181b.js:21 Caught an error: TypeError: Cannot read properties of null (reading '0')
    at googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:17:1316
    at Array.forEach (<anonymous>)
    at p (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:17:1270)
    at Stats (googlesitekit-modules-search-console-7d5307b2d4c3792d6232.js:58:2328)
    at Ih (googlesitekit-vendor-e20382a143485ba05084.js:7:678974)
    at wi (googlesitekit-vendor-e20382a143485ba05084.js:7:724065)
    at ga (googlesitekit-vendor-e20382a143485ba05084.js:7:709669)
    at Zj (googlesitekit-vendor-e20382a143485ba05084.js:7:709594)
    at Lj (googlesitekit-vendor-e20382a143485ba05084.js:7:706940)
    at googlesitekit-vendor-e20382a143485ba05084.js:7:665370 Object

• This reply was modified 2 years, 9 months ago by Jan Dembowski.
• This reply was modified 2 years, 9 months ago by Jan Dembowski.

hello adam

Sorry for the delay in responding. I’m from Petrópolis (Rio de Janeiro, Brazil). My city was hit by the rains and we have been without internet for the last few days. I will answer your questions. Thanks.

The error message appears when we access the “Search Console” tab. In fact, we had already given up on solving this problem since the last time, as we did all the procedures: disabling and uninstalling plugins, asking our hosting provider to do a thorough check.

??

This problem is the same one we have had for some time. We opened a topic about it about 7 months ago. Despite your willingness to help, there was no solution and we ended up giving up for now.
Before there was no such error message reported now. Looks like it’s a new plugin feature. I think…

Hi
I did all the procedures and tests indicated, but the problem remains. So, for now, we’ve given up on finding a solution.
Thank you very much for your willingness to help

Good morning James

This problem is mysterious… We did all the procedures, but without any result.
We installed the diagnostic tool on the subdomain and the same message about file integrity appears there too. But everything works normally.

Hi James

We did the indicated test, but the problem remains.
This error message referring to the CDN also appears in the subdomain classifieds.maxicar.com.br. But everything works there. It seems like an unsolved problem…
I don’t know if this information has any importance: despite our site being in Portuguese, Google Site Kit insists on being installed in English. We have already uninstalled and installed it again in Portuguese, but when it is updated it goes back to English.
Parallel to this, the diagnostic tool, the tool that checks the integrity of files, reports the following:

Looks like some files have been modified.
One possible reason for this could be that your installation contains translated versions. An easy way to fix this is to reinstall WordPress. Do not worry. This only affects WordPress’ own files, not its themes, plugins or media files.

Error /virtual/maxicar.com.br/www/readme.html
Error /virtual/maxicar.com.br/www/wp-includes/version.php

Grateful for the patience!

Hi James

I sent the console error log file through the form.

We use a CDN service (with Cache and Firewall). Both sites, same setup as it’s a subdomain. Name Server Mode. We’ve already tried to disable the entire CDN, without success. Before, everything worked fine this way.

Good afternoon
I forwarded a website profile TXT file generated by the diagnostic tool through the form indicated by you.
Thanks for your interest!

Hello James

Yes, we’ve done all the standard tests. We installed the WordPress diagnostic tool and disabled all plugins and used the default theme.
The diagnostic tool shows us a message about API Rest that I’m not sure is related to the problem:

The REST API is a way that WordPress, and other applications, communicate with the server. One example is the tile editor canvas, which relies on the API to display and save your posts and pages.
The REST API did not correctly process the query context parameter.

We’ve also tried resetting the Google Site Kit and even reinstalling it.
Here are the screenshots.

https://drive.google.com/file/d/1H_MM7PUfS8f5ulJzFKExmF8v3XryOUNQ/view?usp=sharing
https://drive.google.com/file/d/1i156I8pZ7_owFso95AJBQgiDXqguqVMr/view?usp=sharing
https://drive.google.com/file/d/1w1OevSY6PbFNsc4VZLjzz9AmGs_Ujxzo/view?usp=sharing

I thank you for the suggestions. Yes, I will make that attempt. If I have problems, I open a topic to see if I can solve it.

Here in Brazil we say goodbye saying “a hug!” ??

Hi @jamesosborne

When we installed the AMP plugin, it approved the compatibility of all the other installed plugins. But as you are saying, it might be a good idea to investigate this issue further. Any tips?
As for our Herald theme, I consulted the documentation and support before and we were informed that it was compatible with AMP…
We did not get to activate the reader mode. We can try to do that.
We intend to make a new attempt, as we think the AMP version will be important to us.
I thank you for the guidance.