emartens

I have some additional insights into this report.

After some additional debugging, I realized the source of this bug comes from an addition in Woocommerce 7.7.0, a change to line 122 of web/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/StoreApi/Schemas/V1/CheckoutSchema.php

The update replaces this logic:

‘enum’ => wc()->payment_gateways->get_payment_gateway_ids(),

with this logic:

‘enum’ => array_values( wp_list_pluck( WC()->payment_gateways->get_available_payment_gateways(), ‘id’ ) ),

The problem is that this logic calls the get_available_payment_gateways() function which triggers this filter: apply_filters( ‘woocommerce_available_payment_gateways’, $_available_gateways ), and it does it on EVERY REST API call.

This was a problem for our shop, because we were leveraging the woocommerce_available_payment_gateways filter to add custom payment gateways, and the patch made it so that all our wordpress REST APIs executed logic triggered by this filter (logic which was dependent on the existence of the Woocommerce Session Handler, as per my previous comment).

I didn’t see any notes describing this change, but it has BIG implications for anyone leveraging the woocommerce_available_payment_gateways filter in a custom way.

For now our shop will have to patch Woocommerce core until this is fixed. Thank you for your attention to this issue.

Thank you @devnihil

I hadn’t realized more recent versions of the plugin were available, as my wordpress dashboard showed it as up to date.

After applying 19.2.1 version this issue is resolved.

after applying this update, visiting the /wp-admin/ page on our store (and not other admin pages), result in 600 level critical errors bubbling up, and causing the “There has been a critical error on this website” message to appear.

I dont see anything in the changelog for this update which would seem to cause this.