codings

Hello, I am experiencing the same with Version 13.4.1.2. Rolled back to 13.4.1.1 and it’s creating the feed again.

Thank you for this plugin.

Thank you for the detailed reply and for this plugin.

When the AJAX issue was occurring, I was testing different things and didn’t realize the code was still active. So, it turns out that creating a post type breakdown for search results code (I was trying to separate products from the blog posts) didn’t agree with how the theme delivers results. Your reply wasn’t a waste because it led me further into your documentation.

It’s extra work and your documentation is already better than the majority of plugins, but if you can add screenshots to some pages it might help people understand what to expect from the snippets.

Thanks again!

Thanks @missveronicatv

Will try that. Thank you so much for taking the time to reply and provide the snippet!

Sorry about that. When a guest posts comments on blog posts, using various names but the same email address, and then signs up for an account with that email and fills out their UM profile, can the names used on the comments be synced with the name now used on the member account?

Will do. Just updated core and plugins. Will see how it goes. Thanks for everyone’s attention on this thread.

I’m not sure what documentation they pointed to, but this is a MySQL error rather than a PHP one … though it is certainly possible it could be triggered by PHP code interacting with the database.

@barryhughes-1

Sorry for the confusion, I meant MySQL. Must have had PHP on my mind ??

Thank you for the info about the upcoming update. Looking forward to seeing if that stops the errors. But, yes, as you pointed out, at least reverted the previous update stopped the 403s.

I appreciate your time on this and thanks to the entire WC team for the work you all do.

Thanks for checking in! The errors still show, although the site is not throwing 403s anymore after restoring the server to a previous date and updating everything again.

Shared this thread with the host and they redirected me to PHP documentation related to the “Commands out of sync” error, and basically inferred that it’s a WC issue as nothing changed in the hosting environment.

I haven’t replied because there is not much to report back and the errors in the log still persist. I did step 1 and 2, but not step 3. As for contacting the host, they had no server-related issues and they directed me to php documentation that explains Commands Out of Sync. Basically they said it’s a WC issue.

Noticed the WooCommerce plugin update today (9.0.1):

• Fix – Check WC_Legacy_API instead of WC_API as that seems to be cached by lightspeed servers

Since my server is a Lightspeed server and I am using the Lightspeed caching plugin (even though I did test with is disabled), maybe this update will resolve the errors.

Hi @ckadenge, I spent these past few days testing the themes and rolling back as you recommended. I tested two other themes, including the Storefront theme. I thought it did reduce load on the server and resolved the issue temporarily, but then I realized it was probably related to installing WP Crontrol and pausing a few hooks (seems to slow the errors down an reduce server load, but does not stop the errors).

No matter what theme is active, the following errors appear in the debug.log:

[12-Jun-2024 14:34:05 UTC] WordPress database error Commands out of sync; you can’t run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = ‘wc_pending_batch_processes’ LIMIT 1 made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->is_enqueued, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->get_enqueued_processors, get_option

[12-Jun-2024 14:34:05 UTC] WordPress database error Commands out of sync; you can’t run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = ‘woocommerce_hpos_legacy_data_cleanup_in_progress’ LIMIT 1 made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->is_flag_set, get_option

[12-Jun-2024 14:34:05 UTC] WordPress database error Commands out of sync; you can’t run this command now for query UPDATE wp_12345_options SET option_value = ‘1720794845’ WHERE option_name = ‘_transient_timeout_woocommerce_blocks_asset_api_script_data_ssl’ made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Blocks\Assets\Api->update_script_data_cache, set_transient, wp_cache_set, WP_Object_Cache->set, WP_Object_Cache->_transient_set, update_option

[12-Jun-2024 14:39:19 UTC] WordPress database error Commands out of sync; you can’t run this command now for query UPDATE wp_12345_options SET option_value = ‘1720795159’ WHERE option_name = ‘_transient_timeout_woocommerce_blocks_asset_api_script_data_ssl’ made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Blocks\Assets\Api->update_script_data_cache, set_transient, wp_cache_set, WP_Object_Cache->set, WP_Object_Cache->_transient_set, update_option

[12-Jun-2024 16:12:43 UTC] WordPress database error Commands out of sync; you can’t run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = ‘wc_pending_batch_processes’ LIMIT 1 made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->is_enqueued, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->get_enqueued_processors, get_option

I have done this before. The first time I restored the backup, turned on plugins one by one.

I was getting the same errors before turning on HPOS. Why would turning on the “recommended” setting make things worse and add another layer of issues?

The errors above are clearly WooCommerce errors related to Legacy Data Cleanup, WooCommerce Blocks, etc. Why is it running LegacyDataCleanup even when HPOS wasn’t active? How can I stop it from trying to run those scripts every few minutes bringing the site down?

WordPress database error Commands out of sync; you can't run this command now for query SHOW FULL COLUMNS FROM wp_12345_options made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Autoloader\jp12ea33bcea6a641c43d24712adc9f0\Shutdown_Handler->__invoke, Automattic\Jetpack\Autoloader\jp12ea33bcea6a641c43d24712adc9f0\Plugins_Handler->cache_plugins, set_transient, update_option

Jetpack? I don’t even have Jetpack.

The plugin causing the error is: WooCommerce.

Unchecked compatibility mode and these errors are still bringing the site down:

[08-Jun-2024 19:56:19 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'wc_pending_batch_processes' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->is_enqueued, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->get_enqueued_processors, get_option

[08-Jun-2024 19:56:19 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'woocommerce_hpos_legacy_data_cleanup_in_progress' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->is_flag_set, get_option

[08-Jun-2024 19:56:23 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'wc_pending_batch_processes' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->is_enqueued, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->get_enqueued_processors, get_option

[08-Jun-2024 19:56:23 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'woocommerce_hpos_legacy_data_cleanup_in_progress' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->is_flag_set, get_option

[08-Jun-2024 19:56:23 UTC] WordPress database error Commands out of sync; you can't run this command now for query UPDATE wp_12345_options SET option_value = '1720468583' WHERE option_name = '_transient_timeout_woocommerce_blocks_asset_api_script_data_ssl' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Blocks\Assets\Api->update_script_data_cache, set_transient, wp_cache_set, WP_Object_Cache->set, WP_Object_Cache->_transient_set, update_option

Just typed an entire response with a timeline, clicked your gist link to add the system status report, and lost all of what I typed. WP forum links not opening in a new tab by default and not saving what was typed in the editor is frustrating and creates undue waste of time. It always little things like this (and the new style editor) that make me question why I still use this platform.

Sorry for any confusion in the posts above. I was using this thread to keep track of the problem and troubleshooting attempts.

I understand that you have restored the site to its previous state using a backup.

Yes.

Could you clarify why is the site down after it was restored to a previous state?

I restored it, then updated the core and plugins again. The server went back to 503 and the errors (posted above) started filling the log again, each time causing the server resources to spike.

I thought the problem started happening after you enabled HPOS.

No. Originally I did not enable HPOS. I only did so after seeing other posts with similar issues, and started to troubleshoot on my own while waiting for a response here. The problem started after updating WP (6.5.4) and WC (8.9.2). Before this, I did not even know what HPOS was all about, so the Legacy REST API plugin was installed and active. I do not have any webhooks or other known reasons for needing that, so I attempted to switch to HPOS to see if it would fix the 503 problem that occured after updating. Then when I ran the sync, the orders all went to Pending Payment status, so I quickly shut everything down and restored the backups.

Is the HPOS enabled in the backup of the site?

No, it is not enabled in the backup of the site. Restoring the backup took the site back to having the Legacy REST API plugin and WordPress Posts Storage enabled.

But… after restoring, I wanted to try again. I deactivated the Legacy REST API plugin, ran the sync, enabled HPOS, and turned on compatibility mode. The orders did not change status and everything seemed ok, but the same errors are still occurring and the site is still 503ing.

System Status Report

I now have a site that has been down for days. There are others who have posted about similar issues in this forum. After updating, the following errors are causing a resource spikes:

WordPress database error Commands out of sync; you can't run this command now for query UPDATE wp_12345_options SET option_value = '1720413355' WHERE option_name = '_transient_timeout_woocommerce_blocks_asset_api_script_data_ssl' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Blocks\Assets\Api->update_script_data_cache, set_transient, wp_cache_set, WP_Object_Cache->set, WP_Object_Cache->_transient_set, update_option

WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'wc_pending_batch_processes' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->is_enqueued, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->get_enqueued_processors, get_option

WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'woocommerce_hpos_legacy_data_cleanup_in_progress' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->is_flag_set, get_option

HPOS was activated because I was trying everything. There are 0 new orders pending and the site has been down for days, so thanks to the latest WP/WC update, there have been 0 orders for these days. But with HPOS active it caused a sync pending orders queue. When it ran the sync, all the Completed orders went to “Pending Payment” and it sent hundreds of new order emails to the admin email address.

Before it could do further damage and overload email or something else, I told you a restored a previous database and file set, so there is no sync process to finish.

Please help me figure this out. Thank you.

Server error log:

WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'wc_pending_batch_processes' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->is_enqueued, Automattic\WooCommerce\Internal\BatchProcessing\BatchProcessingController->get_enqueued_processors, get_option

WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'woocommerce_hpos_legacy_data_cleanup_in_progress' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->is_flag_set, get_option

WC Status Logs:

Uncaught RuntimeException: Unable to claim actions. Database error. in /12345/site.com/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_wpPostStore.php:696

Server stats:

58 % CPU usage / 170 MB RAM usage / lsphp:site.com/public_html/index.php

Installed the official Action Scheduler plugin. It does nothing so far. Site health: Good. No critical warnings.

Constant 503 errors and overloaded server since updating to WP 6.5.4 / WC 8.9.2. Traffic down, orders stopped, Google sent a notice that they can’t access the site, so it will affect SEO as well.