Barry

I’m not sure there is any need to send that across at present: I was really only suggesting it as a convenient source from which you could copy and paste your list of plugins. Since you’ve determined that the issue persists even when the only plugin present is WooCommerce, though, we no longer need to look at that.

I’m using the default Hello Elementor theme, the issue is still there.

How about with a default theme, such as Storefront or even Twenty Twenty-Four? Again, we don’t see this on our end, so it would seem like something other than WooCommerce is adding it.

?? woocommerce.com/document/how-to-test-for-conflicts

What this plugin/library adds to WordPress is incredibly powerful.

Thank you, Auke!

Hi @odedta,

We don’t see this on our end. Perhaps it is added by another plugin (for example, an SEO plugin)?

If you’d like to share a list of plugins that are installed on your site (you can copy this from the system status report, for instance), we might be able to help you identify the source. Or, you could do some troubleshooting: though we’re not looking for a conflict, as such, following the conflict testing steps might help you identify which plugin is adding this.

Once you know where this is coming from, you can reach out to the support crew for the appropriate plugin ??

I have just been given an invoice generated from the application this generates for my CPU and RAM on the server.

We’re sorry to hear it.

Though it’s already been covered, I will again note that Action Scheduler exists primarily to function as a library that other plugins can choose to use, if they believe it will be helpful. We don’t force anyone to use it.

Additionally, by itself, it shouldn’t incur much overhead at all. It is certainly possible for it to be overloaded but, if so, this is very much the sort of thing those plugins need to address. Action Scheduler just helps them to move work out of the critical path and process it later … the scale and nature of that work, however, is not something it controls.

I did NOT want this plugin, I do not WANT this plugin and I cannot delete this plugin.

Right, but that is again because it is a library that some of your plugins depend on. Generally, one wouldn’t delete a required library from an application: it would stop it from working. If you have concerns about the way some of your plugins are using Action Scheduler, you need to speak to their teams.

If you don’t know which plugins are using it, take a look at the Tools ? Scheduled Actions screen and look at the hook names: these often provide a pretty good clue.

I realize these comments were written a few months back, but I wanted to address a couple of points in case useful for others.

Which is why I say this is a backward method of forcing upon people who really do not need it – and not allowing it to be an optional use case by people who know what they are doing.

From our perspective, we don’t force Action Scheduler on anybody. Generally speaking, we don’t even recommend it be installed directly. Instead, individual plugins choose to bundle it with their code, just as they would do for any other library that they find useful.

Making its use optional, is therefore something that needs to be implemented by the plugins that use it (there is no way for Action Scheduler to do this unilaterally, without causing significant problems).

Hence I understand what benefit you are trying to achieve, but it is very often not required in most cases

I mean, perhaps? We can only assume that the plugin authors who decide to use it do so for reasons that make sense in the context of their project. Otherwise, they would not use it.

Our team also works on WooCommerce, and Action Scheduler is bundled within that plugin. In our case, it’s a deliberate decision: WP’s native scheduled event system does not offer everything we need.

As these tables are not obviously associated to a plugin which is using it through any naming scheme I naturally had no issues with removing such tables.

Deleting database tables needed by an application is always going to be risky so, regardless of whether we’re talking about tables created by Action Scheduler or by some other plugin, I’d caution against doing this directly on a live/production site.

Action Scheduler’s tables are not obviously associated with any other plugin because it is designed to be used by multiple plugins all at once: it’s not uncommon for several plugins to all include and depend on Action Scheduler, but that does not mean each of those plugins should have its own set of scheduled action tables.

• This reply was modified 4 months, 4 weeks ago by Barry. Reason: Small tweaks

I don’t know of any more complete examples, I’m afraid.

9.0.1 is now available, and updating to that version should solve this issue. However, we’d still be really grateful if impacted users could share:

• A list of other plugins that are active, which can be obtained via the System Status Report.
• A note of who your web hosting provider is.

It is depressing that Automattic made this release without testing PROPERLY!!

You’re repeating this in various threads, and I understand your frustration entirely, but I’m not sure it is helpful. We performed extensive testing prior to releasing, and in fact I am not sure if we could reasonably have caught this specific problem ahead-of-time.

A lot of users do not know how to use WP-CLI!!

Please suggest more friendly options.

Perhaps it was missed, but I believe my colleague did also suggest the following:

For many users, manually removing the WooCommerce 9.0 plugin, and re-uploading the WooCommerce 9.0 plugin directory from the?WooCommerce WordPress Plugin Page?fixed the issue.

To expand on this a little more, you don’t necessarily even have to deactivate and delete the plugin to begin with, you can download the latest version, then upload it and overwrite the existing copy via Plugins ? Add New Plugin ? Upload Plugin (then verify you wish to replace the existing version).

However, 9.0.1 is now available, and it may be even easier to simply update to that version.

I hope that helps!

It is hard for casual users to ascertain if the issue is as per: https://developer.woocommerce.com/2024/06/19/developer-advisory-legacy-rest-api-error-in-woocommerce-9-0/

Yes, I agree.

To be clear, I’m not asking @bentaurins or anyone else to verify they have this exact error, I’m just polling for additional information as we scan for patterns.

It is depressing the Automattic can get into this situation on an update. Please trial and test better on .0.0 releases!

I understand your view, here, but please also see my reply over here.

Thanks, no need to post the logs if they are the same sort of errors we already know about.

• Do you mind sharing who your web host is?
• Do you recall if you originally installed WooCommerce via the hosting control panel and, if you can determine this, do you know if plugin updates are being applied at that level?

For those who are happy to share, it could be really useful for us to know:

• What other plugins you are using (this can be obtained from the system status report).
• Who your web host is.
• If you take advantage of an update mechanism like that provided by Softaculous (see comment from @jahrl), or if your host provides some other sort of automated mechanism for this.

Thanks!

@ladysyren even if you can’t share information from your system status report, it could be really useful for us to know who your web host is (if you are happy to share that information)? Thank you!

@sultanstone if you were indeed impacted by the recent Legacy API (9.0) problem, we’d love to gather a little more information if you are happy to share it. In particular, we’d like to know who your web host is. Additionally, it would be great if you could share a note of the other plugins you are using, which you can obtain via your system status report.

We’re sorry for the trouble with 9.0, but are also pretty puzzled by it. If you haven’t already done so and can take a moment to share a note about who your web hosting provider is, and also your system status report (we are particularly interested to know which other plugins are present), we’d really appreciate it. Thank you!

Hi, everyone ?? … if you are impacted by this and are happy to share your system status report and also a note of your web hosting provider, we’d greatly appreciate it.