LovingBro (woo-hc)

Hi @megunticook,

Glad to hear you were able to get it working, and thanks for coming back to share the update. Plugin conflicts can definitely cause some unexpected behavior like this.

I see you’ve marked this as resolved. If anything else comes up, please feel free to start a new thread.

Also, if you have a moment, we’d really appreciate a review of WooCommerce. Your feedback helps other merchants and supports the project: https://wordpress.org/support/plugin/woocommerce/reviews/#new-post

Hi @lykwebsite,

Thank you for testing further and confirming that the issue still occurs even with only WooCommerce active and a default theme enabled. That definitely helps narrow things down and points away from a typical plugin or theme conflict.

Since reinstalling WooCommerce 10.7.0 did not resolve it either, there may be some leftover or mismatched WooCommerce admin assets or database data from the update process causing the admin dashboard scripts to fail.

At this stage, I would recommend the following next steps:

1. Go to WooCommerce > Status > Tools and run:
   Clear WooCommerce cache
   Clear analytics cache
   Delete expired transients
2. Then, manually update the WooCommerce database by clicking the “Update database” button if it appears anywhere in wp-admin.
3. After that, clear your browser cache and any server/CDN cache completely.
4. If the issue still persists, please check whether there are any JavaScript errors visible in the browser console apart from the “store” error and share a screenshot or copy of them with us using https://pastebin.com or https://snipboard.io.

You do not need to recreate the store at this stage. Let us know how the above goes.

Hi @senoryeffo,

Thank you for reaching out about this. I can see how confusing this would be, especially when the order total is far below the $2,500 threshold.

This can sometimes happen if there is incorrect customs data being passed for the shipment, such as the declared item value, HS tariff classification, or package contents.

To help narrow this down, could you please share the following:

1. A screenshot of the customs form and the error message you are seeing, via https://snipboard.io
2. Your WooCommerce Shipping logs, if available
3. Your System Status Report via WooCommerce > Status > Get system report > Copy for support, then paste it to https://pastebin.com or https://quickforget.com and share the link here

You can also try creating a new test order with a very small product value, for example $5, and check if the same message appears.

Once we have those details, we’ll take a closer look with you.

Hi @megunticook,

Thanks for reaching out about this. I just tested this on my end using the customer export download button, and the CSV export was successfully generated and delivered to my email.

Since the export is working generally, if you are not receiving the email on your site, this may be related to the email setup on the site itself, the email being filtered, or possibly a plugin/theme conflict.

Could you please try the following:

1. Check the spam/junk folder for the export email.
2. Temporarily deactivate all plugins except WooCommerce and test the export again.
3. Temporarily switch to a default theme such as Twenty Twenty Four and retest.
4. If you are using an SMTP or email delivery plugin, confirm it is properly configured and not blocking background emails.

Also, please share your WooCommerce System Status Report so we can take a closer look at the site setup: https://woocommerce.com/document/understanding-the-woocommerce-system-status-report/

You can copy the report and share it using https://pastebin.com or https://quickforget.com

Hi @giannisdigitup,

Thank you for reaching out about this. I tested this on my test site running WordPress 7 and the latest WooCommerce version, and I was able to add categories to products successfully using both Quick Edit and the product edit page.

To help narrow down what may be happening on your site, could you please share:

1. A screen recording of the issue using https://loom.com
2. Your System Status Report via https://pastebin.com

You can get the System Status Report from WooCommerce → Status → Get system report → Copy for support.

Once you share those details, I’ll take a closer look into this with you.

Hi @mirconatili,

Thank you for sharing the detailed report and the page links. I checked the category page and can see the issue where the product images are not displaying in the catalog view, while they load correctly on the single product pages.

From what I can see, this looks more likely to be related to either the theme’s WooCommerce template overrides, image regeneration/thumbnails, or a plugin conflict affecting the product loop display on archive pages.

Since you are using the The7 theme with several WooCommerce template overrides, could you please try the following:

1. Go to WooCommerce > Status > Tools and run:
   – Regenerate the product lookup tables
   – Clear template cache
   – Clear transients
2. Regenerate thumbnails using a plugin like Regenerate Thumbnails and then test again.
3. Temporarily switch to a default theme such as Storefront or Twenty Twenty-Four and check if the catalog images appear correctly.
4. If the issue disappears with the default theme, then the issue is likely coming from the The7 WooCommerce template overrides or theme settings.
5. Also temporarily disable image optimization/lazy load related plugins such as Imagify and WP Rocket image optimizations, then retest.

If possible, please also share:
– A screenshot of what you are seeing on your end using https://snipboard.io
– Any browser console errors visible on the affected category page
– A quick plugin conflict test result

That will help narrow this down further.

Hi @mmk175,

Thank you for testing those steps and for confirming the behaviour is still present afterward. It is helpful to know that the issue persists even after clearing transients, caches, and forcing fresh update checks.

At this stage, the behaviour does appear more likely to be related to inconsistent WordPress core update metadata or a partially stuck update state rather than WooCommerce itself directly.

Since the site is currently stable, I would recommend avoiding the “Re-install version 6.3.8-en_US” button again for now, as that package reference appears incorrect and previously triggered the mismatch that caused the wp_register_script_module() fatal error.

The next safest step would likely be to manually refresh the WordPress core files for version 7.0 instead of relying on the reinstall button currently being displayed. This can usually be done safely by:

1. Creating a fresh backup first
2. Downloading a fresh copy of WordPress 7.0 from: https://wordpress.org/download/releases/
3. Replacing only the core WordPress files via File Manager or SFTP, excluding: wp-content wp-config.php

This can help correct any mixed or stale core files that may still be causing WordPress to reference the old 6.3.8 package metadata.

You may also want to ask SiteGround whether they still have any server level object caching or persistent cache layers active beyond the standard cache purge, as occasionally persistent object cache data can survive normal cache clears.

Regarding this notice: “This site appears to be under version control. Automatic updates are disabled.”

That may also be contributing to the unusual update behaviour if WordPress believes the installation is managed under Git/version control or if automatic core updates were previously disabled intentionally.

This guide may help clarify that behaviour further: https://developer.wordpress.org/advanced-administration/upgrade/upgrading/

Please let us know once you have had a chance to test the manual WordPress 7.0 file refresh, or if you notice any further changes afterward.