Payment gateway with handle ‘inpsyde-blocks’ has been deactivated

Resolved martje65
(@martje65)

1 month ago

Sins the Support Moderator have closed our treat (https://wordpress.org/support/topic/backend-log-payment-gateway-with-handle-inpsyde-blocks-has-been-deactivated/ ) herby a new one

Since version 8.1.1 we have the following error messages in our log files.

Backend log: Payment gateway with handle ‘inpsyde-blocks’ has been deactivated in Cart and Checkout blocks because its dependency ‘mollie_block_index’ is not registered. Read the docs about registering assets for payment methods: https://github.com/woocommerce/woocommerce-blocks/blob/060f63c04f0f34f645200b5d4da9212125c49177/docs/third-party-developers/extensibility/checkout-payment-methods/payment-method-integration.md#registering-assets\n

For mollie moderation: https://mollie.inpsyde.com/deactivated_in_blocks is not the solution, if we use the 807 version the paypal payments are not working.

i have looked in the logfiles and in the mollie log file there is nothing, the error log file and Full usage log entry you have the warns.
This is 1 entry from my self, the most are with login on the website.

admin IP adress – – [05/Nov/2025:10:36:28 +0100] “GET /wp-login.php?loggedout=true&wp_lang=nl_NL HTTP/1.1” 200 4463 “https://xxxxx/wp-admin/index.php” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:144.0) Gecko/20100101 Firefox/144.0”
45.156.129.171 – – [05/Nov/20

[Wed Nov 05 10:36:28.536949 2025] [lsapi:warn] [pid 87896:tid 140095024293632] [client admin IP adress] [host http://www.xxxxx.nl] Backend log: Payment gateway with handle ‘inpsyde-blocks’ has been deactivated in Cart and Checkout blocks because its dependency ‘mollie_block_index’ is not registered. Read the docs about registering assets for payment methods: https://github.com/woocommerce/woocommerce-blocks/blob/060f63c04f0f34f645200b5d4da9212125c49177/docs/third-party-developers/extensibility/checkout-payment-methods/payment-method-integration.md#registering-assets\n, referer: https://www.xxxxx.nl/wp-admin/index.php

I dit some more testing and it looks that you get the warning if you logout or login true wp-login.php

If we logout or login thru the Woocommerce login/logout the warning is not there.

So maybe after 13 weeks Side GMBH can provide us with a real solution for this problem?

Viewing 6 replies - 1 through 6 (of 6 total)

Plugin Support Krystian Syde
(@inpsydekrystian)

1 month ago

Hello @martje65

Yes, the thread was closed, but just before that happened, we posted an update with a shared release addressing this exact issue: https://wordpress.org/support/topic/backend-log-payment-gateway-with-handle-inpsyde-blocks-has-been-deactivated/page/4/#post-18807749

https://mollie.inpsyde.com/deactivated_in_blocks is not the solution, if we use the 807 version the paypal payments are not working.

Please ignore the fact that it uses the same version name (807) as before. It is effectively an updated package from 15 of January. Download it from this link. What matters for us now is whether that shared release actually fixes the issue on your site.

Thanks in advance for the clarification.

Kind Regards,
Krystian

Plugin Support Krystian Syde
(@inpsydekrystian)

1 month ago

Hello @martje65

Since linking to the specific post seems to be broken and redirects to an unknown page, here’s the direct link to the package instead: https://drive.google.com/file/d/1fhgB2OKegyTjZhYU4414JR7_u8reXnM1/view

As mentioned before, please ignore the versioning.

Kind regards,
Krystian

Thread Starter martje65
(@martje65)

1 month ago

Dear @inpsydekrystian

It looks that the new 807 version works correct, the errors are gone and Paypal still working.

Plugin Support Krystian Syde
(@inpsydekrystian)

1 month ago

Hello @martje65

Glad it’s finally sorted and sorry it took this long to get there. In case of any further issues let me know.

Kind Regards,
Krystian

rb285
(@rb285)

1 month ago

Works here as well, thank you. Next time it would be a good idea to take another versioning, e. g. 807 => 808 to avoid confusion using the same version number.

Plugin Support Krystian Syde
(@inpsydekrystian)

1 month ago

Hello @rb285

Thanks for confirming it works.

The reason we kept “807” is because it refers to the internal issue number, and we simply updated the package for the same underlying problem without incrementing the version string. I agree it can cause confusion, and we’ll try to handle it more clearly in the future.

Kind Regards,
Krystian

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.