Caleb Burks

You need to contact the people that made the plugin and have them fix the error. There is nothing we can do here, as we do not have any control over that plugin.

The “wooconnector” plugin is causing this. If you temporarily disable the plugin, this error should go away.

You will need to contact those plugin authors.

There’s quite a bit going on there.

Best to perhaps narrow down what is involved in this problem. Usually another plugin or the theme is involved, so follow this guide: https://docs.woocommerce.com/document/woocommerce-self-service-guide/#section-4. You’ll be testing this with only the WooCommerce plugin active and a default WordPress theme. If the errors don’t happen then, you can start to enable things until the errors start happening again.

______

As for the error logs,

PHP Fatal error: require(): Failed opening required ‘C:\wamp64\www\MYDOMAIN\wordpress/wp-includes/class-wp-list-util.php’ (include_path=’.;C:\php\pear’) in C:\wamp64\www\MYDOMAIN\wordpress\wp-settings.php on line 97

You should re-install WordPress because of this recurring one. Go to Dashboard > Updates and click “Re-install now”.

The array() text showed up when only the WooCommerce plugin was active along with a default WordPress theme in use? That seems fairly unlikely as everybody else using this payment gateway isn’t seeing this error. Could you take a screenshot of this happening with the above conditions? (Only WC active and a default WP theme).

And then if it does still happen, have you made any code edits to the WooCommerce plugin itself, or do you have snippets like the above one anywhere else?

_______

As for the code snippet, that is incorrect use of the filter. Just need to return a string:

add_filter( 'woocommerce_cod_icon', 'change_cod_gateway_icon' );
function change_cod_gateway_icon() {
	return '<img src="https://pathtoimage.com/image.png" height="20" />';
}

If you are in control of all products, then it’s really just the billing side of things that needs focus.

PayPal Adaptive Payments used to be perfect for this scenario, but PP seemingly is retiring it by not accepting new signups. https://docs.woocommerce.com/document/paypal-adaptive-payments/#section-9

So instead, this will likely just need a bit of customizations, perhaps using PP Mass Payments: https://www.paypal.com/us/webapps/mpp/mass-payout-payments

Hey Peter,

So you cannot select a shipping class when editing a product here: http://cld.wthms.co/bEBab6? And you are sure shipping is enabled and the product is not virtual?

Also shows in quick edit for me: http://cld.wthms.co/jSgW6h

If you cannot select a shipping class, even for a newly created non-virtual product, then there must be something causing a conflict. Need to temporarily disable all other plugins except for WooCommerce for testing.

You’ve said very little about what was happening 😉

So the problem is that your ajax url is visible? Pretty sure that is unavoidable, at least by default.

Changing the admin location is custom, as will be changing/masking the ajax url.