dpswayne

We found the problem and it’s not with Gutenberg, so please consider this case closed. Another plugin has a “combine javascript files” feature that has worked for over 2 years for us. It seems a recent update, around middle of April, introduced some bug to this feature, which subsequently caused the console error and broke the “menu” button on out site. Nonetheless, it’s not caused by Gutenberg.

Hi, disabling all the plugins would effectively disable out site. Is there any other way to check. If we enable wordpress debug file, would that help you to identify what’s happening? It seems this error is deactivating the “menu” at top right corner of our site, which is an important element, particularly when viewing our site on phones (i.e. small screens).

Hi, I chekced with the developers of the plugin we use and now have found once again, the error is coming from Gutenberg. It seems the line

import*as e from “@wordpress/interactivity”;

is the problem and is found in the file navigation.min.js

You can check our site https://deltapacificvalve.com in a Chrome browser and see the console error. Can you please check to see what’s wrong and how to correct this?

Thanks, Wayne

Hi, thanks for responding. I checked per your advice and then found out the line of code causing the console error is not from your plugin, but rather from Cookie Yes|GDPR Cookie Consent plug-in we use, version 3.2.2. I mistakenly thought it was from Gutenberg because the code specifically referenced Gutenberg. Sorry for the confusion; I notified CookieYes about this. You can see the console error yourself by using a Chrome browser and visiting our page https://deltapacificvalve.com Anyway, thanks for responding and pointing us in the correct direction. Wayne

Adam, sorry, I didn’t have time to finish the submit yesterday, but just finished it. I can tell you more. Today we re-activated SiteKit and our site appears to work. There are no console errors. However, “occasionally”, a page load, whether at the site or inside WP admin will result in a 504 error. After refresh and a little wait, it will then work again. The “impression” I get it activating SiteKit is slowing down the site, causing the timeout. I contacted Network Solutions to inquire/complain about the timeouts, but they’re saying they conducted tests and are not seeing timeouts. Either way, activating SiteKit is causing random 502/504 (mostly 504) errors here and there. Strange. Anything you can find would be appreciated.

Hi Adam,

I’ll send you the Site Health shortly via private form.

Right now, our site has SiteKit deactivated and therefore it loads fine.

“If” we activate SiteKit, then both our front page and wp-login page start to fail loading. The first time you try it, it appears to load normally, but after entering password, etc., it takes forever and eventually fails. Then subsequent visits to the front page or wp-login page result in either an Error 502 or 504.

“If” we go in via FTP and disable SiteKit plugin, the site returns to normal.
SiteKit was the only plug-in update yesterday, resulting in the failure, so we’re confident this plugin is causing the problem.

I’m going to set up a staging site, which will be exactly the same as our current site later and activate SiteKit inside it. Then you can check the staging site to see what happens and if there are any console errors. I’ll email you when it’s done, and I’ll check as well.

Thanks,
Wayne

TYVM