Error API packages

Hi @mkbarraco!

Thanks for reaching out to us.

This kind of fatal error is usually caused by a conflict with your theme or with another plugin. The best way to determine this is to:

• Temporarily switch your theme to Storefront
• Disable all plugins except for WooCommerce
• Repeat the action that is causing the problem

If you’re not seeing the same error after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated.

Reactivate the theme first and check again. Then, go on and reactivate your other plugins one by one, testing after each, until you find the one causing conflict.

You can find a more detailed explanation on how to do a conflict test here:

https://docs.woocommerce.com/document/how-to-test-for-conflicts/.

Thanks!

• This reply was modified 3 years, 2 months ago by Mirko P..

Hi @rainfallnixfig, thanks for your help!

I received an email from you, but inside I can read different words. In the email, you suggest me to check about Woocommerce Block plugin. Wich is missing in my client’ website.

Anyway… I followed your guide, but the issue still here. It comes and go, I can’t see it on every page load.

Hi @mkbarraco,

In the email, you suggest me to check about Woocommerce Block plugin. Wich is missing in my client’ website.

This error comes from the core block functions, not the added WooCommerce Blocks plugin, which is why the previous reply was edited. ??

When you tested for conflicts, did the same thing happen with only WooCommerce enabled and no other plugins?

What steps do you take to get the error? Is it while browsing the site, editing a page, something else?

Could you also please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.? Once you’ve done that, paste it here in your response.

Thanks!

Hi there,

I received an email from you, but inside I can read different words

As explained by my colleague, I edited the response after having focused more on the error and realized that the WooCommerce blocks function was the one built-in with core WooCommerce and not the one added via the external WooCommerce Blocks plugin.

Said that, we haven’t really heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Thanks.