Update from version 2.9.0 to 2.9.1 Breaks Site

It’s on auto-update and I have received several emails that the update has failed.

Hello @suitsjen

Thank you for letting us know.

Could you please share the stack error from your email or from the WooCommerce status logs?

It’s likely that a conflict with another plugin is causing this issue. Without the error log, it’s difficult to pinpoint the exact source. Please try disabling all plugins except for WooCommerce and PayPal Payments, then update the plugin again. After that, enable each plugin one by one to identify which one is causing the conflict.

If you need the previous version of the plugin, you can find it here: Previous Version 2.9.0.

Kind Regards,

Krystian

I’m not sure which report you need. There is nothing that says “stack report.” Here are a few with fatal errors.

Hello @suitsjen

Thank you for providing this.

So far, we have only had one report on our support board with a similar issue, but we haven’t received any information back from that user regarding what caused it. I would appreciate it if you could conduct a conflict test and let us know which plugin might be causing this behavior.

Let me know how it goes or if you need any further assistance.

Kind Regards,

Krystian

Subscriptions for WooCommerce is where your plugin is having problems. I also discovered that both versions 2.9.1 and 2.9.2 will cause the conflict.

Here is the full error from my hosting account:

[2024-10-02T19:49:05.410425+00:00] PHP Fatal error:? Uncaught TypeError: WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package::addModule(): Argument #1 ($module) must be of type WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Module\Module, Wps_Subscriptions_Module given, called in /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244#012Stack trace:#012#0 /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(37): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->addModule(Object(Wps_Subscriptions_Module))#012#1 /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}(‘/nas/content/li…’)#012#2 /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init()#012#3 /nas/content/live/hac2024stg/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\{closure}(”)#012#4 /nas/content/live/hac2024stg/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)#012#5 /nas/content/live/hac2024stg/wp-includes/plugin.php(517): WP_Hook->do_action(Array)#012#6 /nas/content/live/hac2024stg/wp-settings.php(555): do_action(‘plugins_loaded’)#012#7 /nas/content/live/hac2024stg/wp-config.php(119): require_once(‘/nas/content/li…’)#012#8 /nas/content/live/hac2024stg/wp-load.php(50): require_once(‘/nas/content/li…’)#012#9 /nas/content/live/hac2024stg/wp-blog-header.php(13): require_once(‘/nas/content/li…’)#012#10 /nas/content/live/hac2024stg/index.php(17): require(‘/nas/content/li…’)#012#11 {main}#012? thrown in /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php on line 244

Hello @suitsjen

Thank you for providing the error details.

I’m aware that the PayPal Payments plugin is causing this issue, but this is not happening without the influence of an external factor, such as another plugin. The plugin itself doesn’t trigger this type of error on its own, as it would affect all users, not just you. We need to verify what specific factor is causing this conflict.

If you disable all other plugins, the issue should not occur, as one of them is having a problem with our modularity update. We need to identify which one to help you resolve the issue. If you encounter any problems with running a conflict test, let us know and we can assist you.

You can reach out to us directly for further help. Here’s how you can request support: Request Support. Please make sure to include the URL of this thread in your ticket for reference.

Kind Regards,

Krystian

I’m not sure what you are asking me to do. I’ve done the conflicts test and found that Subscriptions for WooCommerce is where your plugin is having problems. I also discovered that both PayPal Payments versions 2.9.1 and 2.9.2 will cause the conflict.

Hello @suitsjen

I apologize for the confusion. Could you please confirm whether you are referring to the “Subscriptions for WooCommerce” plugin? It’s important for us to verify, as the term can be used flexibly and doesn’t exactly point out the plugin name.

In this case, I would recommend contacting the developer of that plugin directly. It’s up to them to address this issue because we changed our system to a modular architecture, but older Dhii modules should still work the same way as before.

Please note that we officially support only the WooCommerce Subscriptions plugin, so it is up to the third-party developers to ensure compatibility with our plugin. Its quite similar situation like with YITH plugin raised here: https://www.ads-software.com/support/topic/critical-error-in-2-9-1-php-7-4-wordpress-6-2-2/

While we are sorry for the inconvenience, unfortunately, we are unable to provide a direct fix for this conflict.

Kind Regards,

Krystian

Hello @suitsjen

Since we have not received any further communication from you, we are assuming that your issue has been resolved.

Therefore, we mark this thread as resolved. If you still have any questions or if a new problem arises, don’t hesitate to open a new thread.

Kind regards,
Krystian