LovingBro (woo-hc)

Hi @thecottonshoppe,

Thank you for the screenshot and the additional details. I can see what you mean here. The quantity selector is displaying two sets of plus and minus buttons, which would explain why the quantity is increasing and decreasing by 2 instead of 1.

Based on what I’m seeing, this is unlikely to be a WooCommerce core issue and is more commonly caused by a theme or plugin conflict where multiple quantity button scripts are being loaded on the same product page.

Could you please try the following:

1. Temporarily switch to a default WordPress theme such as Twenty Twenty-Five (or test on a staging site if available) and check whether the duplicate buttons disappear.
2. Perform a conflict test by disabling all plugins except WooCommerce and WooPayments, then re-enable them one at a time until the issue returns.
3. Since I can see you’re using Elementor and the site appears to use additional frontend enhancement plugins, pay particular attention to any plugin that customizes product pages, quantities, AJAX add to cart functionality, or WooCommerce layouts.

That should help us narrow down exactly which component is responsible.

Hi @agent3w,

Thank you for taking the time to follow up and share what ultimately resolved the issue on your OpenSUSE Tumbleweed installation.

It’s great to hear that installing the Noto font packages resolved the display problem. We also appreciate the additional observation regarding the character usage in the WooCommerce files. Your findings provide useful context for anyone who may encounter similar font rendering issues on Linux environments where the required fonts are not available by default.

As you’ve marked the topic as resolved, I’ll go ahead and consider this one closed. Thank you again for your detailed testing and for sharing the outcome with the community.

Your feedback can help other merchants who are considering WooCommerce or looking for guidance from real store owners about their experience with the plugin. If you have a moment, we’d appreciate a review of WooCommerce: https://wordpress.org/support/plugin/woocommerce/reviews/#new-post

Thanks again for your contribution and for helping document the solution.

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 WordPress.org 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://wordpress.org/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://wordpress.org/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://wordpress.org/plugins/woocommerce/

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