Another one 🙁
2024-01-10T17:59:13+00:00 CRITICAL Uncaught TypeError: WooCommerce\PayPalCommerce\ApiClient\Entity\PaymentSource::name(): Return value must be of type string, null returned in /www/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-api-client/src/Entity/PaymentSource.php:50
Stack trace: 0 /www/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-button/src/Helper/ContextTrait.php(182): WooCommerce\PayPalCommerce\ApiClient\Entity\PaymentSource->name() 1 /www/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-session/src/Cancellation/CancelController.php(66): WooCommerce\PayPalCommerce\Session\Cancellation\CancelController->is_paypal_continuation() 2 /www/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-session/src/SessionModule.php(57): WooCommerce\PayPalCommerce\Session\Cancellation\CancelController->run() 3 /wordpress/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\Session\SessionModule->WooCommerce\PayPalCommerce\Session{closure}(”) 4 /wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) 5 /wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 6 /www/wp-content/plugins/woocommerce/includes/class-woocommerce.php(712): do_action(‘woocommerce_ini…’) 7 /wordpress/wp-includes/class-wp-hook.php(324): WooCommerce->init(”) 8 /wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) 9 /wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 10 /wordpress/wp-settings.php(646): do_action(‘init’) 11 /www/wp-config.php(117): require_once(‘/wordpress/wp-s…’) 12 /wordpress/wp-config.php(5): require(‘/www/wp-config….’) 13 /wordpress/wp-load.php(50): require_once(‘/wordpress/wp-c…’) 14 /wordpress/wp-blog-header.php(13): require_once(‘/wordpress/wp-l…’) 15 /www/index.php(17): require(‘/wordpress/wp-b…’) 16 {main}
thrown in /www/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-api-client/src/Entity/PaymentSource.php on line 50
Hello @dorogoff
I have seen a thread with this error three times, but each time none of the users were able to provide a system report, so it’s hard to properly analyze it. In light of this, I will paste my previous post because it contains key information. The key thing is to know if you can reproduce this problem.
If you can reproduce it, I recommend disabling all other plugins except WooCommerce and PayPal Payments to see if the problem persists.
If the error does not occur with only WooCommerce and PayPal Payments active, you should then re-enable the other plugins one by one. This process will help identify which plugin is causing the conflict.
If an immediate solution is needed you might consider reverting to the previous release of the plugin to see if that resolves the issue.
Additionally, we must have a complete view of your system setup to provide more specific assistance. You can get this report from your WooCommerce environment by navigating to WooCommerce > Status > Get system report > Copy for support.
Once you have copied the report, please share it with us securely. You can upload the log files to our PrivateBin at PrivateBin. After uploading, share here the link, and we’ll review the logs in detail.
In case you prefer not to share these details publicly, feel free to open a ticket with our service desk for more private and direct support. Here’s how you can request support: Request Support. Please include the URL of this thread in your ticket for reference.
We appreciate your cooperation in this matter.
Kind Regards,
Krystian
I am getting this error as well, but very intermittently. It attaches to a specific user and will error out every time they try to load a page while logged in.
This is going to be a hard problem to reproduce because it is so intermittent. I’m not sure the dev team is going to be able to wait for a website with a clear-cut, reproducible case.
But I can tell you an apparent workaround: as an admin user, “View As” the user who is having the issue.
From walking through the stack trace, it looks like there is a bad “order” attached to the user’s session. This bad “order” lacks a name. By invoking “View As”, my theory is that this bad session data is flushed.
I don’t know how the bad order is created. If we could figure that out, it might point toward a reproducible case. Perhaps an aborted PayPal order?
Is there a better issue tracker to which I could contributor? I’m a developer and would be happy to try to help track this down.
