Dustin L.

Thank you. I implemented the:

define( 'WPE_GOVERNOR', false );

…code yesterday. I didn’t get the KILLED QUERY notice overnight and the site is still standing, so I guess it is okay.

Hi @mosesmedh

Thanks for your help!

We have received on average 7 orders per day so far this year.

Here is the info you requested:

fatal-errors-2025-02-21.log
https://pastebin.com/LL8g5N9Z

plugin-woocommerce-2025-02-24.log
https://pastebin.com/zsBEmYsM

SystemStatusReport_redacted.com_2025-02-24T17-21-04.txt
https://pastebin.com/DSbc5wT8

The last fatal errors report was on February 21. The same KILLED QUERY errors occurred today (February 24), so I’m not sure that the fatal errors are a factor.

One thing that may be involved:

This store has been around since before HPOS. In December, I enabled HPOS with compatibility mode. It was on for a few days until I discovered a problem. At that time, I switched back to WordPress posts storage (legacy) and disabled compatibility mode.

Could this be a left over process from then? The store has over 11,000 orders.

Thank you

Please disregard this request.

I understand why the VideoObject schema was added to the page now.

There isn’t a video embedded on the page but we do link to a video. I guess that is why the VideoObject schema is added.

I no longer need help.

@registriran By the way, installing the previous version, 2.0.66, will fix the problem.

I’m having the same issue and reported this to the support team earlier today.

You are right. This is resolved now.

Thanks

Does on_all_plugins() really need all of the logic it has now? Since you already know the directory and filename for the plugin, can’t this be made much simpler?

public static function on_all_plugins( $all_plugins ) {
    $all_plugins[ 'woocommerce-legacy-rest-api/woocommerce-legacy-rest-api.php' ][ 'Description' ] = 'The legacy WooCommerce REST API, which is now part of WooCommerce itself but will be removed in WooCommerce 9.0.';
    return $all_plugins;
}

…That seems to fix the issue on my system.

I think the original code is causing problems when I am on a Windows server.

I found out how to reproduce it. The bug only seems to be present on my local development environment: Laragon.

I installed a fresh copy of WordPress, WooCommerce, and WooCommerce Legacy REST API and the same issue occurred.

I noticed the active plugin has the description: The legacy WooCommerce REST API, which used to be part of WooCommerce itself but is removed as of WooCommerce 9.0.

…which is found in the typical plugin header of woocommerce-legacy-rest-api.php.

The phantom plugin has a different description: The legacy WooCommerce REST API, which is now part of WooCommerce itself but will be removed in WooCommerce 9.0.

…which is found in \includes\class-wc-legacy-rest-api-plugin.php

/**
* Handler for the all_plugins hook, used to change the description of the plugin if it's seen before June 2024.
*/
public static function on_all_plugins( $all_plugins ) {
    $plugin_relative_path = str_replace( WP_PLUGIN_DIR . '/', '', self::$plugin_filename );
    $all_plugins[ $plugin_relative_path ][ 'Description' ] = 'The legacy WooCommerce REST API, which is now part of WooCommerce itself but will be removed in WooCommerce 9.0.';
    return $all_plugins;
}

…which is called by:

// 1717192800 = June 1st, 2024
if( time() < 1717192800 ) {
    add_action( 'all_plugins', self::class . '::on_all_plugins' );
}

For some reason, my installation is showing both descriptions.

Thank you for getting back to me.

The problem only exists on a local development version of our production site.

I don’t know how to reproduce the problem.

To troubleshoot, I created a copy of the site and changed the theme to Twenty Twenty-Four and deleted all plugins except WooCommerce & WooCommerce Legacy REST API. I also deleted all transients and deleted the uninstalled_plugins and active_plugins options.

There is nothing else in my plugins folder:

View post on imgur.com

The phantom entry is still there:

View post on imgur.com

Any other ideas?

It turns out her browser was automatically translating the page to German. When it did that, it changed the $ sign to the € sign. It didn’t change the amount.

She disabled the translation and the price was displayed as it should be.

I’m sorry! I created this thread under the PayPal plugin by accident. I am actually using your Stripe plugin:

https://www.ads-software.com/plugins/woo-stripe-payment/

It is the only payment gateway enabled on the site.

Could your Stripe plugin be showing Euros to our customer? Any other thoughts on this?

Sorry for the confusion.

I think there is a misunderstanding. I’m sorry if I did a poor job of explaining the problem.

The issue is not with the legacy REST API feature. I understand it is included in WC 8.8.3 and doesn’t need an extra plugin to function.

The issue I am reporting is related to the legacy_rest_api_usages log. When I enable the legacy REST API plugin v1.0.4, the log stops recording entries – even though the legacy REST API is still receiving requests and functioning as expected.

Hi @doublezed2

Thank you for getting back to me.

That’s not entirely correct.

Things had been working fine with WooCommerce and the new Legacy REST API plugin version 1.0.1.

We use a 3rd party app the connects to the legacy REST API typically at least a few times per day, and I had been seeing daily log entries.

Here are some examples:

2024-04-24T01:43:26+00:00 Info Version: 2, Route: /wc-help-scout, User agent: WooCommerce API Client-PHP/2.0.1, IP: 52.5.170.16
2024-04-25T18:13:46+00:00 Info Version: 2, Route: /wc-help-scout, User agent: WooCommerce API Client-PHP/2.0.1, IP: 52.6.41.205
2024-05-09T21:22:06+00:00 Info Version: 2, Route: /wc-help-scout, User agent: WooCommerce API Client-PHP/2.0.1, IP: 52.6.41.205

Then, on May 9, I deactivated, uninstalled, reinstalled, and reactivated the Legacy REST API plugin. I was trying to solve this issue:

https://www.ads-software.com/support/topic/plugin-listed-two-times-in-installed-plugins-list/

Side note: The issue described on that link is not present on our production site. It’s only on a development site, so I don’t think it is related to this issue. I only made the change to keep our development and production sites in sync.

Back to the original issue: Around May 14-15 I noticed that there had been no new legacy_rest_api_usages log entries since May 9.

I reached out to the 3rd party vendor who told me they hadn’t made any changes to their app. As far as they knew, it still required the legacy REST API.

I tried deactivating the legacy REST API plugin, and disabling the Legacy REST API feature in the WooCommerce setting. Doing that caused the 3rd party app to stop pulling in data from the API. It also cause a new log entry to appear.

I re-enabled the legacy REST API & the plugin, and the log entries stopped.

I updated the legacy REST API plugin to 1.0.4.

Now there are no log entries regardless of whether I enable or disable the legacy REST API setting.

The last step I tried was deactivating the WooCommerce Legacy REST API plugin, but keeping the legacy REST API setting enabled in WooCommerce (8.8.3). This fixed the problem.

Now log entries appear as expected.

So I think the problem is with the WooCommerce Legacy REST API plugin. Enabling it breaks the logging of legacy_rest_api_usages on our site.

Nevermind.

I updated WordPress and now the extra entry has disappeared.

@paktas I ended up using a 3rd party plugin for schema. It works great.

https://www.ads-software.com/plugins/schema-and-structured-data-for-wp/