I’m getting a critical error – Is this compatible with latest WordPress version

Hello @kristinubute

The error is most likely related to the woocommerce_form_field filter being used incorrectly on our admin pages. This issue is often caused by third-party plugins, such as some Checkout Field Editor plugins, that modify WooCommerce checkout form fields. It’s crucial to ensure that any custom code executing this filter only runs on the checkout page and not on the admin pages. It’s also difficult to point to any plugin directly since we don’t have your system report.

To address this, I recommend conducting a full conflict test. Please disable all other plugins except for WooCommerce and PayPal Payments. This step is crucial to isolate the cause of the issue. For a more detailed guide on how to perform these tests, please refer to:?How to test for conflicts.

If the issue persists after performing these steps, we suggest you contact us directly for further assistance. We may need to examine your system report or logs to better understand what’s happening. You can open a ticket with our service desk. 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

Hi, I can’t deactivate the plugins on the live site so can’t test the plugins individually at this stage.

Site is still working but keep getting 503 errors intermittently. ERROR log suggested your plugin.

Can I send you some logs or system file separately via email in order to do some further investigation please?

Could it be your current version of plugin not compatable with latest wordpress version?

Have other people had similar issues/error like this?

I can’t get a full backup either at this stage to restore to a TEMP TEST SITE either … so I’m trying different things.

Your plugin allows clients to pay via paypal yes?

Paypal is still working, a recent order for customer just came through.

Please advise

Thanks

Hello @kristinubute

To investigate this further, we would greatly appreciate it if you could send us your system report and any relevant fatal error logs. You can submit these details through our support request form at?Request Support.

Could it be your current version of plugin not compatable with latest wordpress version?

I can confirm that our plugin is fully compatible with the current version of WordPress.

Have other people had similar issues/error like this?

There has been another thread where a similar problem was raised.

Your plugin allows clients to pay via paypal yes?

It’s important to note that this issue should not affect payment operations on your page. It seems to be a mismatch with another plugin rather than a direct problem with payment flow.

Please don’t hesitate to reach out through the provided support link with any additional questions or concerns you may have.

Kind Regards,

Krystian

Thanks for your reply

I’ll send through via email the full System Report for Woocommerce/Wordpress

Here is a fatal error log

2023-11-29T13:33:49+00:00 CRITICAL Uncaught TypeError: Return value of WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer::render_multiselect() must be of the type string, null returned in /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php:188
Stack trace: 0 /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/WCGatewayModule.php(549): WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer->render_multiselect(NULL, ‘wwlc_state’, Array, ”) 1 /home/test/public_html/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\WcGateway\WCGatewayModule::WooCommerce\PayPalCommerce\WcGateway{closure}(NULL, ‘wwlc_state’, Array, ”) 2 /home/test/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array) 3 /home/test/public_html/wp-content/plugins/woocommerce/includes/wc-template-functions.php(3021): apply_filters(‘woocommerce_for…’, NULL, ‘wwlc_state’, Array, ”) in /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php on line 188

2023-11-29T13:40:02+00:00 CRITICAL Uncaught TypeError: Return value of WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer::render_multiselect() must be of the type string, null returned in /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php:188
Stack trace: 0 /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/WCGatewayModule.php(549): WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer->render_multiselect(NULL, ‘wwlc_state’, Array, ”) 1 /home/test/public_html/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\WcGateway\WCGatewayModule::WooCommerce\PayPalCommerce\WcGateway{closure}(NULL, ‘wwlc_state’, Array, ”) 2 /home/test/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array) 3 /home/test/public_html/wp-content/plugins/woocommerce/includes/wc-template-functions.php(3021): apply_filters(‘woocommerce_for…’, NULL, ‘wwlc_state’, Array, ”) in /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php on line 188

2023-11-29T15:05:21+00:00 CRITICAL Uncaught TypeError: Return value of WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer::render_multiselect() must be of the type string, null returned in /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php:188
Stack trace: 0 /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/WCGatewayModule.php(549): WooCommerce\PayPalCommerce\WcGateway\Settings\SettingsRenderer->render_multiselect(NULL, ‘wwlc_state’, Array, ”) 1 /home/test/public_html/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\WcGateway\WCGatewayModule::WooCommerce\PayPalCommerce\WcGateway{closure}(NULL, ‘wwlc_state’, Array, ”) 2 /home/test/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array) 3 /home/test/public_html/wp-content/plugins/woocommerce/includes/wc-template-functions.php(3021): apply_filters(‘woocommerce_for…’, NULL, ‘wwlc_state’, Array, ”) in /home/test/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsRenderer.php on line 188

I am using Wholesale Prices Premium plugin but they have said it has nothing to do with their plugin.

And both plugins are activated and still working. It’s just I get this ERROR in error logs and Fatal Error.

I am sending the latest LOGS to you via your SUPPORT TICKET

Thanks

I’ve just sent it to support now.

Hello @kristinubute,

As informed in the private engagement: The error you’re experiencing is related to a conflict between the WooCommerce PayPal Payments plugin (version 2.4.1) and the WooCommerce Wholesale Lead Capture plugin by Rymera Web Co (version 1.11). The issue arises because the WooCommerce Wholesale Lead Capture plugin is using the woocommerce_form_field filter on pages that are not related to its functionality, including the PayPal Payments settings pages. This is evident from the wwlc_state reference in the stack trace of the error, that we found in the logs you provided.

To resolve this issue, the WooCommerce Wholesale Lead Capture plugin needs to limit the usage of the woocommerce_form_field filter to only its frontend pages. This adjustment will prevent the filter from interfering with the operation of other plugins, such as the WooCommerce PayPal Payments plugin.

We will mark this thread as resolved. If you require additional support, please continue our communication with us via the private engagement.

Kind regards,
Joost

HI, Please keep this ticket open for now until I have contacted them.
That would be appreciated. Thanks

BUT we are NOT using Version 1.11 anymore.

We are using V 1.17.6

So are you still correct with what you are saying, as you ment9ioned 1.11 V and that is NOT active anymore at all.

And still the error.

Please advise.

Hello @kristinubute

that statement only says we confirmed the issue to be caused with the use of the version 1.11, not that it was resolved after that release. My advice would be to try another plugin instead, or reach out to the plugin developer to see if they can get a fix in place for this issue.

Kind regards,
Joost