WooCommerce PayPal Payments breaks wordpress

UPDATE: I rolled back WooCommerce to 6.8.2 and “WooCommerce PayPal Payments” to 1.9.3 and the sytem error disappeared.

There must be a problem in one (or both) plugin between the working versions (see above) an the last available (at the time of writing: 7.1.0 for WooCommerce and 2.0.0 for “WooCommerce PayPal Payments”.

Please consider fixing the problem.

Alberto

Hi @nolixo,

This error is a compatibility issue that’s usually caused by a third-party plugin or theme modification. But the next PayPal Payments update 2.0.1 includes a fix for it.

A pre-release version of the new update is available from here if you’d like to give it a try before the official release later this week.

Kind regards,
Niklas

This potential conflict should be resolved now with the latest PayPal Payments update 2.0.1. Please give it a try and let us know if any issues persist for you with the new version.
Thanks!

Kind regards,
Niklas

Sorry to tell you but I just tested it (2.0.1) and looks like the problem is still there. The whole site is broken (message: “There has been a critical error on this website …”).

To fix it I have to login in recovery mode and deactivate the plugin, or roll it back to 1.9.5.

I’m running the 6.1.1 wordpress version with all the plugins up to date. The plugins are:

• Classic Editor
• Complianz | GDPR/CCPA Cookie Consent
• Jetpack
• Jetpack Protect
• TranslatePress – Multilingual
• W3 Total Cache
• WooCommerce
• WooCommerce Dropbox
• WP Mail SMTP
• WP Menu Cart
• WP Rollback

Here is the error log:

An error of type E_ERROR was caused in line 66 of the file [...]/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Gateway/OXXO/OXXO.php. Error message: Uncaught TypeError: Argument 1 passed to WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\OXXO::WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\{closure}() must be of the type array, null given, called in [...]/wp-includes/class-wp-hook.php on line 308 and defined in [...]/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Gateway/OXXO/OXXO.php:66 Stack trace: #0 [...]/wp-includes/class-wp-hook.php(308): WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\OXXO->WooCommerce\PayPalCommerce\WcGateway\Gateway\OXXO\{closure}(NULL) #1 [...]/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array) #2 [...]/wp-content/plugins/woocommerce/includes/class-wc-payment-gateways.php(163): apply_filters('woocommerce_ava...', Array) #3 [...]/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/Tasks/Payments.php(93): WC_Payment_Gateways->get_available

Hi @nolixo,

Thanks for the feedback. It looks like this potential compatibility problem could occur both on line 66 (as in your report) and on line 88 in the mentioned file.

This behavior was only softened up for line 88 in the latest update 2.0.1 though, and line 66 remained as before. So the error persists for you.
The team will address this in the next update in January, but the cause of the error is still likely a compatibility problem with a third-party plugin.

Performing a full conflict test may help isolate the cause of potential issues with the theme or a different plugin. Here’s a guide that explains the troubleshooting steps in more detail: How to test for conflicts
Please let us know how this works out for you. Thanks!

Kind regards,
Niklas

Hi there,

I double-checked this with our developers, and this issue will be resolved in the next update in the second half of January, likely version 2.1.0.
Since there’s a path to a solution, and we haven’t head back from you, I’ll mark this thread resolved.

For any further questions, please feel free to reopen this thread or create a new one. Thanks!

Kind regards,
Niklas