This quote of the first response to your linked post makes it clear that the bug is in WooCommerce.
You’re correct in identifying the issue. In WooCommerce 10.1.0, the method $order->get_report_customer_id() is being called in DataStore.php (line 541), but this method no longer exists in the WC_Order class. It was deprecated and removed in earlier versions, and
its reappearance here is unintended
. This is causing the critical error you’re seeing in your logs.
It is unclear to me why Frank would continue to suggest that you disable the Frisbii payment gateway after recognizing that the bug is in WooCommerce. Maybe in lack of understanding that the payment gateway is not an un-essential analytics extension. As for the 2 later responses that claim the bug is in the Frisbii plugin; they look very “routine” driven and possibly AI generated. I invite you to open the profiles of those two agents and see their profile creation dates, post counts and non-existing websites.
There are no references to get_report_customer_id() in the Frisbii module. Those calls come from within WooCommerce it self originating in its sync_order API endpoint. We will however have a workaround to avoid using this WooCommerce endpoint ready in next release of the Frisbii module.
