dimitrisv

The peculiar thing is that – as most – I had never installed 8.8.1 in the first place.

We only got notified for a new version with the 8.8.2 release!

Anyway, the suggested, radical changes promise to make our sites much much more faster. Lets see – less than a month to go.

Just to convey here that in our case the resolution was as follows:

1. Downgrade to Woocommerce 8.7. As you downgrade in our case you will get errors like this:

WordPress ?κδοση 6.5.2
Ενεργ? θ?μα: Presidential Noble (?κδοση 1.0.0)
Τρ?χων πρ?σθετο: WooCommerce (?κδοση 8.7.0)
?κδοση PHP 8.2.18



Λεπτομ?ρειε? σφ?λματο?
===========================================
?να σφ?λμα τ?που E_ERROR εντοπ?στηκε στη γραμμ? 226 του αρχε?ου public_html/wp-content/plugins/woocommerce/includes/wccom-site/class-wc-wccom-site.php. Κωδικ?? σφ?λματο?: Uncaught Error: Failed opening required 'public_html/wp-content/plugins/woocommerce/includes/wccom-site/rest-api/endpoints/class-wc-rest-wccom-site-status-controller.php' (include_path='.:/usr/share/php') in public_html/wp-content/plugins/woocommerce/includes/wccom-site/class-wc-wccom-site.php:226
Stack trace:
#0 public_html/wp-includes/class-wp-hook.php(324): WC_WCCOM_Site::register_rest_namespace()
#1 public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#2 public_html/wp-content/plugins/woocommerce/includes/rest-api/Server.php(60): apply_filters()
#3 public_html/wp-content/plugins/woocommerce/includes/rest-api/Server.php(43): Automattic\WooCommerce\RestApi\Server->get_rest_namespaces()
#4 public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\RestApi\Server->register_rest_routes()
#5 public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#6 public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#7 public_html/wp-includes/rest-api.php(597): do_action()
#8 public_html/wp-includes/rest-api.php(555): rest_get_server()
#9 public_html/wp-includes/rest-api.php(2922): rest_do_request()
#10 [internal function]: rest_preload_api_request()
#11 public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Settings.php(143): array_reduce()
#12 public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Internal\Admin\Settings->add_component_settings()
#13 public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#14 public_html/wp-content/plugins/woocommerce/src/Internal/Admin/WCAdminSharedSettings.php(61): apply_filters()
#15 public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(268): Automattic\WooCommerce\Internal\Admin\WCAdminSharedSettings->Automattic\WooCommerce\Internal\Admin\{closure}()
#16 public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(384): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->execute_lazy_data()
#17 public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->enqueue_asset_data()
#18 public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#19 public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#20 public_html/wp-admin/admin-footer.php(95): do_action()
#21 public_html/wp-admin/update.php(186): require_once('...')
#22 {main}
  thrown

2. Re upgrade to 8.8.2

No issue will be present.

Me thinks that the issue was indeed due to various code merging issues in Woocommerce 8.8.1 and 8.8.2 in conjunction with 8.7 – So the paypal payments plugin was not at fault.

I guess this has to do with the major refactoring/re-engineering of the whole Rest-api infrastructure to be released next month.

The funny thing is that @inpsydekrystian had suggested to go to 8.8.1 and retry, which I did but to no avail. In other cases I either went back to 8.7 (and had the paypal payments plugin activated) or remained in 8.8.2 (without the paypal plugin).

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

Yes they are working on it as we speak. I gave to the guys access in a problematic (for their plugin) installation and are looking into it.

Fingers crossed they will sort it out soon.

Yes I know but the initial feedback I got from that plugin’s team is that since the crash is reported by woocommerce, then it is woocommerce etc. Also at the time I had no further input from them.

Today the informed me that they had sent a jira invite in my request for support, I couldn’t find it, they sent me a new one and I gave access to our beta installation and are trying to figure it out right now.

First of all HUGE and HUBLING apologies!

Indeed the message had gone to the spam folder of my email (outlook btw) – its originating domain did not help either.

Yes I will provide you with full access (and sftp access) to our beta sites/server for you to have a look and hopefully sort out the issues.

I have never received a response from you! This is why I am complaining in here.

Please resend it to me your response. Or tell me who is suppossed to be the sender to check the junk folder.

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.ads-software.com

I read your humbling response @konamiman

You are an exceptional person so you are bound to be an exceptional developer!

I don’t blame you – who would have thought that woocommerce will be in the business of hair and nail colours and that their operators would think that they can add as many attributes with 100s of terms? I couldn’t contemplate it either.

Actually, I had advised them to create common attributes for say colours but they had insisted that the say number “7.2” colour of one company is different from the “7-2” colour of another company. So I had advised them to do at most 40-50 products like that.
A few months later I noticed these 400 attributes.

Anyway, now that we have realised that the platform is so good that it attracts the usage by people that have no sense of proportion, let see what we can do.

I am not a php developer. Although I write my own stuff, php is just one of the 40 languages I can converse with in my 44 year history in computing. What I am saying is that my coding in php is amateurish, so I cannot help you on this. I was invited to your business (e-commerce) because my theories in accurately predicting electoral outcomes by a friend (the owner of that eshop) who allowed me to try to apply these theories to predicting (if not shaping) shopping behaviours. Then came the need to make a platform “my own” so that I can help shops run faster and then get the data etc etc. I chose woocommerce (due to wordpress) and the open source concept behind it.

Having said that, ANY help you need I am here to help. I can definately give you access to our beta testing server so that you can experiment/develop with our dataset etc. As we know reality can be a lot worse that our imagination.

Many thanks also to @jacklynbiggin for mobilising the best person to address the issue.

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

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}

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

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 ??

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

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

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).

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 ?