LovingBro (woo-hc)

Hi @masterfox5,

Thanks for reaching out about this. I can see how the current cart behavior in your Avada theme setup could make the shopping experience less clear for customers, especially on mobile where the cart is tucked away inside the menu.

WooCommerce itself does support cart item counts and cart visibility, however, the display and placement of the cart icon are usually controlled by the active theme. Since you’re using the Avada theme, this behavior is likely coming from the theme’s header and mobile menu configuration.

I’d recommend checking the Avada Header Builder and mobile menu settings to see if the cart icon and cart counter can be enabled or repositioned there. Avada’s support documentation may help with that setup as well: https://avada.com/documentation/

You can also test temporarily with a default WordPress theme such as Storefront to compare the behavior. If the cart count appears correctly there, that would further confirm the issue is theme related rather than WooCommerce itself.

Please let us know what you find after checking the Avada settings.

Hi @justing87,

Thanks for sharing the details here, and I can understand how confusing this must be, especially when you’ve inherited a site you didn’t originally build.

From the error message, it looks like the Shippo Shipping integration is trying to use a Parcel ID that no longer exists on the Shippo side. In many cases, this can happen if cached shipping data, outdated shipping settings, or a plugin conflict is causing WooCommerce to reference an invalid Shippo parcel object.

To help narrow this down, please try the following:

1. Go to WooCommerce → Settings → Shipping and review the Shippo Shipping settings, then reconnect/re-authenticate the Shippo account if that option is available.
2. Clear any caching layers on the site, including caching plugins, server cache, or CDN cache if used.
3. Temporarily switch to a default theme like Storefront or Twenty Twenty-Four and deactivate all plugins except WooCommerce and the Shippo Shipping plugin, then test checkout again. This helps determine whether another plugin or the current theme is interfering with the shipping request.
4. Please also share a copy of your WooCommerce System Status Report so we can check the current environment and active extensions:
   WooCommerce → Status → “Get system report” → “Copy for support”. You can paste the report using: https://pastebin.com or https://gist.github.com

Once you share the report and the results of the conflict test, we’ll take a closer look from there.

Hi @josklever,

Thank you for sharing this feedback and for the additional context around the changelog visibility. You do raise a very valid point here, especially for store owners updating from 10.7.0 directly to 10.8.1, where the current presentation could make the update appear much smaller than it actually is.

At the moment, it does appear there may have been an issue on ww.wp.xz.cn that caused version 10.8.0 to temporarily stop showing, possibly related to the submission and release process for 10.8.1, which may explain why users briefly saw 10.7.0 as the latest available version again.

I also checked the developer section here: https://ww.wp.xz.cn/plugins/woocommerce/#developers, when clicking “See changelog for all versions”, the complete changelog does still appear correctly here: https://raw.githubusercontent.com/woocommerce/woocommerce/trunk/changelog.txt

I’m glad to hear your client sites updated to 10.8.0 without issues earlier, even when some other merchants did. Please kindly update to the latest version 10.8.1 which fixes the issue experienced by some merchants.

Feel free to get back to us if you need any further support. Cheers!

Hi @tobet,

Thank you for taking the time to share this detailed accessibility feedback and for including the WCAG Technique H2 reference along with your example page.

I can see your concern regarding the separate links for the product image and title within the [products] shortcode output, and how this may lead to repetitive navigation for screen reader and keyboard users.

Could you also let us know which theme you are currently using on the site? The theme and any WooCommerce template overrides it includes may influence the frontend markup and accessibility behavior being output for the products shortcode.

Hi @ronbi13,

Thank you for bringing this up. I just checked on my end as well, and I can confirm that the latest version currently showing on the plugin page is indeed 10.7.0: https://ww.wp.xz.cn/plugins/woocommerce/

I understand the concern, especially for sites that already updated to 10.8.0. At the moment, I would recommend not making any manual changes or downgrades on those sites unless you are actively experiencing issues.

I will go ahead and escalate this internally so the team can take a closer look at what happened with the 10.8.0 release visibility and provide further clarification.

We will update this thread as soon as we have more information.

Hi @momo-fr and @vasilisweb,

Thank you both for chiming in and sharing your experience with this update issue.

At the moment, this appears to be related to some WooCommerce 10.8.0 updates not completing fully on certain sites, which can leave some files missing or out of sync temporarily during the update process.

Based on the reports shared here so far, including @captaincrank’s workaround, it does appear safe to update to 10.8.0. In cases where the error occurred, rolling back to the previous WooCommerce version and then running the update again has successfully resolved the issue for several users.

In many cases, simply reinstalling or updating WooCommerce again is enough and a full reinstall is not always necessary. You can download a fresh copy here if needed: https://ww.wp.xz.cn/plugins/woocommerce/

Before updating, please make sure you have a full backup available and, if possible, test first on a staging site.

Hi @paul2411,

Thank you for sharing the screenshot and confirming that the issue also occurs with the default Twenty Twenty-Five theme active. The console error is very helpful here.

Since the issue persists during onboarding, the next important step would be to perform a complete plugin conflict test, including temporarily disabling any active MU plugins as well, since MU plugins remain loaded even during standard plugin testing.

Please try the following:
– Deactivate all plugins except WooCommerce and WooPayments
– Temporarily disable the custom MU plugins located under /wp-content/mu-plugins/
– Keep the default Twenty Twenty-Five theme active
– Then retry the WooPayments onboarding flow and test the dropdown fields again

I noticed several custom MU plugins and custom checkout related functionality in the SSR, so it would be important to rule those out completely before we conclude this is a WooPayments regression.

If the issue still happens after the full conflict test, please let us know and we’ll continue investigating further from there.

Hi @vasilisweb,

Thanks for the detailed follow-up questions, you’re understanding the process very well already, and your summary is mostly correct.

If you do not see any HPOS incompatibility notices under WooCommerce > Settings > Advanced > Features, that is usually a good sign that your active plugins declare HPOS compatibility. Still, it’s always recommended to test carefully, especially on a staging site if possible.

About synchronization, yes, when you enable compatibility mode, WooCommerce synchronizes orders between the legacy posts tables and the HPOS tables. WooCommerce handles this in the background using scheduled actions.

You can monitor the synchronization progress under: WooCommerce > Status > Scheduled Actions

You may see actions related to order synchronization there while the migration is running. Depending on the number of orders, it may take some time.

Your understanding of the process is correct overall:

1. Check whether your plugins support HPOS
2. Update plugins/themes/WooCommerce to the latest versions
3. Enable compatibility mode so orders sync between both storage systems
4. Wait for synchronization to complete
5. Switch the authoritative storage to HPOS
6. Keep compatibility mode enabled for some time if you are unsure about older plugins
7. Once fully confident all plugins work correctly with HPOS, you can disable compatibility mode

And yes, if a plugin is not HPOS compatible and no update is available from the developer, then you may eventually need to replace it with an alternative that supports HPOS properly.

As for whether HPOS is mandatory, currently WooCommerce still allows legacy storage, so your site should continue functioning. However, HPOS is the future direction of WooCommerce order storage and brings better scalability and performance, especially for larger stores.

Over time, more plugins and WooCommerce features will be optimized around HPOS, so migrating eventually is recommended.

You can also review the official guide here for additional details: https://woocommerce.com/document/high-performance-order-storage/