Crashes after update to 8.8.2

Hello @dimitrisv

This output seems unrelated to our plugin and pertains instead to the WooCommerce Standard Gateway. The WooCommerce plugin includes built-in support for PayPal among its standard payment gateways, and this is what is being referred to in the error output.

We recommend contacting WooCommerce directly regarding this matter, for example, through their support page here: https://woocommerce.com/my-account/create-a-ticket/

If you believe the situation is different, please let us know. Since you mention that you “deactivated” the plugin, and I’m a bit confused about the source. It would be good to know what you have actually deactivated.

Should you have any more questions, feel free to reach out.

Kind regards,
Krystian

Hello,

The crashes stopped as soon as disabled your plugin. As the error log suggests the error is due to changes in the logging of woocommerce that your gateway does not adhere to.

Please create the ticket yourselves because it is your gateway that is impacted.

Our free, open sourced troubleshooting has to have some limit you see, as this benefits YOUR business.

We can live for a few days without paypal.

Best regards,

Dimitris.

• This reply was modified 7 months, 1 week ago by dimitrisv.
• This reply was modified 7 months, 1 week ago by dimitrisv.

Hello?@dimitrisv

As the error log suggests the error is due to changes in the logging of woocommerce that your gateway does not adhere to.

Could you please share the part of the output where you think there’s a connection to the PayPal Payments plugin? As I’m not seeing any.

/www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/gateways/paypal/includes/settings-paypal.php(58): WC_Log_Handler_File::get_log_file_path(‘paypal’)

The error is thrown in the PayPal Standard location provided by WooCommerce during the PayPal gateway initialization (class-wc-gateway-paypal.php). The error message involving the PayPal setup within WooCommerce suggests that there’s a problem with WooCommerce’s implementation or an integration issue between WooCommerce and its included PayPal gateway functionality. This confirms the hypothesis that the error appears after updating WooCommerce itself.

The crashes stopped as soon as disabled your plugin.

Just to confirm, disabling the WooCommerce PayPal Payments plugin stopped the fatal error?

Looking forward to your response.

Kind regards,
Krystian

Correct! After disabling YOUR plugin the errors ceased.

That means our site does not offer Paypalpayments since yesterday night.

We didnt know that Woocommerce offers native support of paypal – we are only using yor plugin for paypal.

I guess you have to speak to them.

I opted to write here because it is your service that it is impacted, for Woocommerce support, you are merely of one their functionalities. So, I presumed, here is the best place to sort this out ASAP, as you may have other back channels with the Woocommerce core team.

Am I clear now?

• This reply was modified 7 months, 1 week ago by dimitrisv.

Hello @dimitrisv

Could you try reinstalling the previous version of WooCommerce, and then update it to the latest version again?

Sometimes files can get corrupted during the update process. Re-downloading and reinstalling WooCommerce can replace the corrupted files with fresh ones.

Let us know the outcome.

I opted to write here because it is your service that it is impacted, for Woocommerce support, you are merely of one their functionalities. So, I presumed, here is the best place to sort this out ASAP, as you may have other back channels with the Woocommerce core team.

I see your point, but initially, I don’t see any connection to our plugin, so we need to verify that. Please note, that there have been no reports of this fatal error. Considering our user base, it seems unlikely to be a widespread issue; it’s probably an isolated incident. Therefore, it requires basic analysis first before escalating it directly to the developers.

Kind regards,
Krystian

In our case, I have to point out that, version 8.8 and 8.8.1 never appeared as updates!

Only just yesterday we were notified to update from version 8.7.0 o the latest version.

I guess you have to ask the Woocommerce team to release a version that 8.8.3 to make up for this for most eshops.

In our case we have over 10 eshops that we are supporting and doing triple installs to all of them is a bit of a pain – thanks to this bug we noticed in the first one, all the others have stayed in 8.7.
I will only do this for the one that got corrupted. But what if I need also version 8.8.0 ?

What I will do first is to upgrade an 8.7 eshop to the 8.8.1 version.
If the error does not occur… (it first occurs during installation) then we are on the right track. If not I will have to try (in another store going to version 8.8.0 etc).

Sadly the issue also occurs when upgrading to version 8.8.1 from version 8.7

I couldn’t find in the repo version 8.8 (only the rc1)

My apologies for the tone earlier but when I see that this plugin is by Woocommerce and you are telling that I have to write to woocommerce plugin I got a bit frustrated.

Please post in here when the issue will get resolved. I will revert the shop I just did to 8.7.0

Just to confirm that by downgrading to 8.7 there was no reported issue. That rules out the possibility of the conflict being introduced by the latest version of your plugin in the interim period (between 8.7 release and the release of you 2.6.1).

So please talk to them and figure it out why this error occurs when your plugin is present on both 8.8.1 and 8.8.2

Cheers!

• This reply was modified 7 months, 1 week ago by dimitrisv. Reason: spelling

Hello @dimitrisv

My apologies for the tone earlier but when I see that this plugin is by Woocommerce and you are telling that I have to write to woocommerce plugin I got a bit frustrated.

Our plugin is the official WC PayPal integration, but please note that we are not WooCommerce per se. We are the company that develops the PayPal Payments plugin. I wanted to clarify this detail, although it’s not crucial to our current discussion.

So please talk to them and figure it out why this error occurs when your plugin is present on both 8.8.1 and 8.8.2

The key issue is that I can’t replicate this problem on my end, and we haven’t received any other tickets about it. Each version of our plugin undergoes thorough QA testing to ensure compatibility with the latest WooCommerce version, so this seems to be an edge case.

We’ll need more details about your site and a system report to assist you further. Please contact us directly for more help. You can submit a support request and include your system report or logs for us to review. To open a ticket with our service desk, follow this link: Request Support. Be sure to mention this thread’s URL in your ticket for reference.

Looking forward to hearing from you.

Kind regards,
Krystian

Thanks Syde!

I just sent the ticket, with system report and my business email for further talk.

Please note that this installation, which is the default php 8.2 / Maria DB 10.6 for Cloudways, is common to all our stores. So you see the issue appeared in another store as well etc.

Also note that in our installation we have also reported in the past a problem with your plugin during order processing that again, only appears to impact us.

Any problems we have faced are mainly due to the particular version of the php and Maria DB, in possible conjunction with Varnish/REDIS that we are using for caching – plus other performance optimizations. In the speed up challenge of Cloudways, all of us “winners” made a woocommerce site with over 10k products and 500 categories load in less than 150ms. NitroPack – sponsoring #WCEU 2024 on X: “Congratulations to the winners of the #WooCommerce speed up challenge! ??” / X (twitter.com)

Mind you we boast to have one of the fastest woocommerce sites around. See for example this metric for a product with 268 variations (loading 0.8 seconds) :
Archived Performance Report for: https://femme-fatale.gr/product/nychia/imimonima-vernikia/xromata/aloha-imimonimo-verniki-eight-colo… | GTmetrix

So maybe we are over doing it… and bringing your code to its limits. But sorting it out with us is bound to be beneficial to you too ??

May I also confirm that upon disconnecting of the merchants acccount with paypal, the issue was not observed (after update to 8.8.2)

Instead we got this:

[Thu Apr 18 18:52:36.159415 2024] [proxy_fcgi:error] [pid 13161:tid 139856634156800] [client 2a01:4b00:f61e:2700:5194:70a4:10c0:76a2:0] AH01071: Got error ‘PHP message: PHP Fatal error: ?Uncaught Error: Class “Automattic\\WooCommerce\\Admin\\RemoteSpecs\\DataSourcePoller” not found in /public_html/wp-content/plugins/woocommerce/src/Admin/DataSourcePoller.php:14\nStack trace:\n#0 /public_html/wp-content/plugins/woocommerce-payments/vendor/jetpack-autoloader/class-php-autoloader.php(90): require()\n#1 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/PaymentGatewaySuggestions/PaymentGatewaySuggestionsDataSourcePoller.php(10): Automattic\\Jetpack\\Autoloader\\jpc77c6f448183a14790ec1fee9fc3636e\\PHP_Autoloader::load_class()\n#2 /public_html/wp-content/plugins/woocommerce-payments/vendor/jetpack-autoloader/class-php-autoloader.php(90): require(‘/home/850962.cl…’)\n#3
public_html/wp-content/plugins/woocommerce/src/Admin/Features/PaymentGatewaySuggestio…’, referer: https://glowthes.gr/wp-admin/update-core.php?action=do-plugin-upgrade



Obviously this has to do with other payment engine via “jetpack-autoloader” and it seems to me that the changes that Woocommerce does for their payment methods adversely impact this plugin.

• This reply was modified 7 months, 1 week ago by dimitrisv. Reason: removed directory path
• This reply was modified 7 months, 1 week ago by dimitrisv. Reason: removed directory path

To clarify… The error in the previous message was recorded in the error logs.

Via email we just got this error:

?να σφ?λμα τ?που E_ERROR εντοπ?στηκε στη γραμμ? 14 του αρχε?ου /public_html/wp-content/plugins/woocommerce/src/Admin/DataSourcePoller.php. Κωδικ?? σφ?λματο?: Uncaught Error: Class “Automattic\WooCommerce\Admin\RemoteSpecs\DataSourcePoller” not found in /public_html/wp-content/plugins/woocommerce/src/Admin/DataSourcePoller.php:14

Stack trace: 0 /public_html/wp-content/plugins/woocommerce-payments/vendor/jetpack-autoloader/class-php-autoloader.php(90): require() 1 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/PaymentGatewaySuggestions/PaymentGatewaySuggestionsDataSourcePoller.php(10): Automattic\Jetpack\Autoloader\jpc77c6f448183a14790ec1fee9fc3636e\PHP_Autoloader::load_class() 2 /public_html/wp-content/plugins/woocommerce-payments/vendor/jetpack-autoloader/class-php-autoloader.php(90): require(‘/home/850962.cl…’) 3 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/PaymentGatewaySuggestions/Init.php(60): Automattic\Jetpack\Autoloader\jpc77c6f448183a14790ec1fee9fc3636e\PHP_Autoloader::load_class() 4 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/Tasks/AdditionalPayments.php(183): Automattic\WooCommerce\Admin\Features\PaymentGatewaySuggestions\Init::get_suggestions() 5 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/Tasks/AdditionalPayments.php(125): Automattic\WooCommerce\Admin\Features\OnboardingTasks\Tasks\AdditionalPayments::get_suggestion_gateways() 6 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/Tasks/AdditionalPayments.php(104): Automattic\WooCommerce\Admin\Features\OnboardingTasks\Tasks\AdditionalPayments::has_enabled_other_category_gateways() 7 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskList.php(305): Automattic\WooCommerce\Admin\Features\OnboardingTasks\Tasks\AdditionalPayments->can_view() 8 [internal function]: Automattic\WooCommerce\Admin\Features\OnboardingTasks\TaskList->Automattic\WooCommerce\Admin\Features\OnboardingTasks{closure}() 9 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskList.php(302): array_filter() 10 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskList.php(171): Automattic\WooCommerce\Admin\Features\OnboardingTasks\TaskList->get_viewable_tasks() 11 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskLists.php(349): Automattic\WooCommerce\Admin\Features\OnboardingTasks\TaskList->is_visible() 12 [internal function]: Automattic\WooCommerce\Admin\Features\OnboardingTasks\TaskLists::Automattic\WooCommerce\Admin\Features\OnboardingTasks{closure}() 13 /public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskLists.php(346): array_filter() 14 /public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Onboarding/OnboardingSetupWizard.php(217): Automattic\WooCommerce\Admin\Features\OnboardingTasks\TaskLists::get_visible() 15 /public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Internal\Admin\Onboarding\OnboardingSetupWizard->component_settings() 16 /public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() 17 /public_html/wp-content/plugins/woocommerce/src/Internal/Admin/WCAdminSharedSettings.php(61): apply_filters() 18 /public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(268): Automattic\WooCommerce\Internal\Admin\WCAdminSharedSettings->Automattic\WooCommerce\Internal\Admin{closure}() 19 /public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(393): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->execute_lazy_data() 20 /public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->enqueue_asset_data() 21 /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 22 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 23 /public_html/wp-admin/includes/template.php(2228): do_action() 24 /public_html/wp-admin/update.php(53): iframe_footer() 25 {main}

I see that you didn’t seem to bother with the issue in here.

So I reposted it there with some additional comments about your… “service”

Crashes with Woocommerce Paypal payments after 8.8.2 | www.remarpro.com

Hello @dimitrisv

I believe I advised you to reach out to our support board, which you did. We have responded and are awaiting your reply. Please check your email. Typically, we continue conversations on the private board under these circumstances.

I’m not sure where the conclusion came from in the thread you linked that we aren’t taking responsibility for this issue. If you look at the content of our message on Jira Support Management, you’ll see that we requested assistance to reproduce this issue.

Also, please note that we are not available on weekends, as our support hours are Monday through Friday.

Looking forward to your response.

Best regards,
Krystian