Matt

Thanks Michelle — I have submitted support ticket #4445231

Hi Michelle, thanks for the response, but it is not related to caching on the host at all, because the UTM parameters are correctly sent to Google Analytics when we’re using version 8.23.1.

The issue only occurs when we update the plugin to version 8.24

Awesome, thanks for the quick turnaround!

@gonsurfn77 Hmmm that sounds like it may be unrelated?

I would try downloading the Woocommerce plugin fresh from the www.remarpro.com plugin repository and uploading all of the files again. If that doesn’t work I’d be willing to take a look and help you out.

@gonsurfn77 Anywhere should be fine in the functions.php file for the fix I posted. I would try undoing both though and see if that error still persists.

@gonsurfn77 The code would be placed in functions.php of your theme.

AMAZING find dasbuilder. Looks like it’s calling out to some external server for “remote notifications” and just hanging forever… Never knew this was a part of Woocommerce, but adding the following code to my functions.php file should disable that and fix the issue:

add_filter('woocommerce_admin_features', 'pk_woocommerce_admin_features');
function pk_woocommerce_admin_features($features) {
	if(($key = array_search('remote-inbox-notifications', $features)) !== false) {
		unset($features[$key]);
	}
}

This has been fixed in version 8.0 — there is now a function that checks for both Gutenberg and the Classic Editor plugin: should_load_gutenberg_assets().

Thanks guys

I think I’ve found the issue.

In the file /wordpress-seo/admin/class-admin-asset-manager.php on line 178 is the function scripts_to_be_registered there is a check on line 196 for Gutenberg.

It is checking for Gutenberg based on if a function used to enqueue Gutenberg scripts exists, which as long as it’s enabled will exist.

It seems like there needs to either be a hook added for us to make use of or for check for the Classic Editor plugin and if Gutenberg is disabled or not to be added.

The issue can be temporarily fixed by just adding “&& false” to the if statement on line 196. Hopefully a patch is added in the next version of Yoast.

Testing on another site, it looks like setting ‘credentials_ok’ to 1 instead of ‘active’ may be the only option as active gets unset somewhere if ‘credentials_ok’ isn’t 1

Spend 20 minutes trying to figure out a solution and you figure one out 2 minutes after posting.

I just threw another .htaccess file in the directory and whitelisted the file

That did indeed fix the issue, thank your (other) Barry.