Artem Yanin

Hello, @mollieintegration
We are using orders API
I don’t think it’s good to publish a complete list of our plugins from the security point of view of our store.
We are using woocommerce with HPOS and this error we receiving on standard orders page. By text of the error i can tell you that it looks almost same issue as you had with 7.4.1-again mess in Payment/Order objects, but now in another place

Hello, I have the same error since update to 7.4.1, 7.4 hasn’t this error.
i can combine it with log from mollie log file:

[25-Jan-2024 23:00:34 UTC] PHP Fatal error: Uncaught Error: Call to undefined method Mollie\Api\Resources\Payment::isCompleted() in public_html/wp-content/plugins/mollie-payments-for-woocommerce/src/Payment/MollieOrderService.php:153

2024-01-25T23:00:34+00:00 DEBUG mollie_wc_gateway_ideal: Mollie payment object tr_NSgBSwNgYH (live) webhook call for order 623764.
2024-01-25T23:00:34+00:00 DEBUG Mollie\WooCommerce\Gateway\MolliePaymentGateway::handlePaidOrderWebhook – mollie_wc_gateway_ideal: Order 623764 does not need a payment by Mollie (payment tr_NSgBSwNgYH).
2024-01-25T23:00:34+00:00 DEBUG Mollie\WooCommerce\Payment\MollieOrderService::processRefunds called for order 623764 / paymenttr_NSgBSwNgYH
2024-01-25T23:00:34+00:00 DEBUG Mollie\WooCommerce\Payment\MollieOrderService::processRefunds: No refunds to process for order 623764 / paymenttr_NSgBSwNgYH
2024-01-25T23:00:34+00:00 DEBUG Mollie\WooCommerce\Payment\MollieOrderService::processChargebacks called for order 623764 / payment tr_NSgBSwNgYH
2024-01-25T23:00:34+00:00 DEBUG Mollie\WooCommerce\Payment\MollieOrderService::processChargebacks: No chargebacks to process for order 623764 / payment tr_NSgBSwNgYH

I can see that customer started payment 3 times, and one of the payment was completed.

This errors coming for same order ID.

Good afternoon, now it certainly works ?? We will be glad to receive feedback with wishes /criticism/questions about the plugin. Our email [email protected]

It can’t be fixed because you doing live requests to your api..
if ( '' != self::$access_key ) {
so if key empty-there will be no self::$account_info at all, it will be null without key. And then you doing

function ws_admin_credits_notice(){
            if ( 2 > WC_Sendinblue::$account_info['email_credits']

using isset(WC_Sendinblue::$account_info['email_credits']) before 2 >…. already will fix it, but i don’t wanna do it every update.. so set debug mode to true, remove key, visit page like dasboard-u’ll see notice. Use code i gave or better solution..

And also i found this code in account_info api

if ( false == $account_info || false === $account_info ) {

It has 0 sense, guys.. And it makes me feel scared about other parts of code.. be better, guys ??

• This reply was modified 3 years, 11 months ago by Artem Yanin. Reason: typo

Plugin reactivation didn’t help, server has no caches, with key/without same warning