v7.5.4 auto activated network plugin

[Yorlinq]

I use this plugin in a WordPress NETWORK for years now. Suddenly (v 7.5.4) the plugin is NETWORK ACTIVATED end all sub sites that are not using WooCommerce are getting the error:

Deze plugin kan niet worden geactiveerd omdat vereiste plugins ontbreken of inactief zijn.

ENGLISH:
This plugin cannot be activated because required plugins are missing or inactive.

Surely that's because these sub sites don't have WooCommerce activated.

Please fix this. I reverted back to 7.5.3 >> That version work correct.

[asotela3911]

Hi @Yorlinq
Thank you for reporting this issue. However, there seems to be a misunderstanding regarding the recent update to version 7.5.4 of the plugin.

There is no issue with the 7.5.4 update concerning network activation. Here's a detailed explanation:

The WordPress Multisite feature allows you to manage multiple WordPress sites from a single installation. You can find more about it here: https://learn.wordpress.org/tutorial/introduction-to-wordpress-multisite-networks/. Within a Multisite network, plugins can be activated individually for each site or enabled for all sites from the network admin. The Mollie plugin does not have the capability to “network activate” itself after an update, and we are confident that this did not happen automatically.

Regarding the error message:
“Deze plugin kan niet worden geactiveerd omdat vereiste plugins ontbreken of inactief zijn.”

This message appears when WooCommerce is not active on the site or network-wide. In version 7.5.4, WooCommerce is declared as a plugin dependency, meaning the Mollie plugin will not activate unless WooCommerce is active. You can read more about plugin dependencies here: https://make.wordpress.org/core/2024/03/05/introducing-plugin-dependencies-in-wordpress-6-5/.

If WooCommerce is not active on certain sub-sites, the dependency feature in version 7.5.4 is functioning as intended by preventing the Mollie plugin from being activated.

There is no issue with the plugin itself that needs fixing. If you have further concerns or need assistance, please open a support ticket with the Mollie Support Team. https://www.mollie.com/gb/contact/merchants
We will be happy to assist you further.

[Yorlinq]

I know how it works... as I wrote: I've been using WordPress networks for years.

Your plugin v 7.4.5 is NETWORK ACTIVATING automatically regardless if WooCommerce is even activated on the subsite.

[Yorlinq]

So I guess you're just gonna ignore this bug..?

[Yorlinq]

There will probably come a day when more people will notice this and you DO take this bug seriously.

So I'll try one more time to make it clear to you what the problem is.

In a WordPress network environment, you can choose to enable a plugin NETWORK WIDE via the MAIN SITE (the plugin is always enabled on all sub sites) or you can choose to enable/disable a plugin PER SUB SITE.

Logically, this last option is the case with the Mollie app because not every sub site has the WooCommerce plugin enabled. So the Mollie plugin is only activated manually on the sub sites that actually have the WooCommerce plugin active.

However, in your latest update, WordPress sees the Mollie plugin as NETWORK ACTIVATED while that is not the case. This way, you will then receive the logical message on ALL SUB SITES where WooCommerce is NOT active: "You must activate WooCommerce before you can use this plugin."

So this is a bug. Our network setup has NOT changed in recent months and this issue arose after the update of your plugin.

I would like it if I were taken seriously at all. Use it to your advantage instead of dismissing me with a copy/paste answer for dummies.

[asotela3911]

Dear @Yorlinq,

Apologies for my late reply. Let us investigate this issue in more detail, and we will get back to you. We might have some time this week to look into it. We will keep you updated on our findings and the steps we are taking to resolve this matter.

[Yorlinq]

Any update on this? I won't update unless this issue is fixed.

PS. Version 7.5.3 is ok.... after that it went wrong.