Thanks for reporting the issue. As @saivutukuru said, some plugins had a compatibility issue with WooCommerce 10.5.0 that caused this issue. Can you try updating to 10.5.1 and check if the issue is fixed for you? Thanks in advance!
Thanks a lot for the details, @rb285, it’s very useful! It’s difficult to say which plugin might be interfering with the add-to-cart form because it’s a long list, and I don’t know all of them.
But given that there appear to be several reports about plugins being incompatible with WooCommerce 10.5, it’s possible we will ship an update in 10.5.1 where the chances of incompatibilities are mitigated. I would suggest staying in 10.4.3 until 10.5.1 is released.
Do you know at least one customer using a productive environment who has no problems with 10.5.0?
Yes, most stores updated without problems, and there are plenty of live stores using WC 10.5.0 with no issues. However, given that variety of plugins out there, there is always the chance that a certain combination might be problematic when enhancements are introduced in WC core. We always try to reduce the chances of this happening and actively communicate when a change might impact existing stores.
A few questions to better figure out what’s going on:
Can you confirm the issue only happens in variable products?
Can you share your SSR or the list of plugins you are using?
If you have some custom code that might impact the add-to-cart form, that might be relevant as well.
Do you have a URL where the issue can be reproduced? Can you check if the add-to-cart-variation.min.js?ver=1.5.0 script is loaded?
WooCommerce 10.5 introduced a change that disables the add-to-cart button in the PHP template and enables it via the script. That was done because several users requested the button to be disabled while the script is being loaded.
However, if the WooCommerce script is dequeued, enabling the button needs to be done by whichever other script the store is using. You can read more about it here:
Heads-up that WooCommerce 10.5 introduced an update to the variable products template and script.
I wasn’t able to reproduce the issue with PPOM, but if any of the plugins installed is dequeuing the default script while using the default template, that might be the cause.
Hi there, @hugo1405. Thanks for opening this issue!
Let me ask a few questions to better figure out what’s going on:
Can you confirm the issue only happens in variable products?
Can you share your SSR or the list of plugins you are using?
If you have some custom code that might impact the add-to-cart form, that might be relevant as well.
Do you have a URL where the issue can be reproduced? Can you check if the add-to-cart-variation.min.js?ver=1.5.0 script is loaded?
WooCommerce 10.5 introduced a change that disables the add-to-cart button in the PHP template and enables it via the script. That was done because several users requested the button to be disabled while the script is being loaded.
However, if the WooCommerce script is dequeued, enabling the button needs to be done by whichever other script the store is using. You can read more about it here:
Let me ask a few questions to better figure out what’s going on:
Can you confirm the issue only happens in variable products?
Can you share your SSR or the list of plugins you are using?
If you have some custom code that might impact the add-to-cart form, that might be relevant as well.
Do you have a URL where the issue can be reproduced? Can you check if the add-to-cart-variation.min.js?ver=1.5.0 script is loaded?
WooCommerce 10.5 introduced a change that disables the add-to-cart button in the PHP template and enables it via the script. That was done because several users requested the button to be disabled while the script is being loaded.
However, if the WooCommerce script is dequeued, enabling the button needs to be done by whichever other script the store is using. You can read more about it here:
I indeed want to set a custom page as the WooCommerce Shop page and I already tried what you explain here: go to WooCommerce → Settings → Products and set the Shop Page as my store page.
That’s good! Can you confirm that if you click on Visit Store from the admin, the correct page is opened?
But… what do you mean by this: ‘Make sure that WooCommerce blocks/widgets are added to that page if needed’?
This might vary a little bit depending on the theme you are using and whether you are using Gutenberg (the WordPress’ default editor) or Elementor.
First of all, you will need to know if your theme is a block theme or a classic theme. You will know you are using a block theme if you see Appearance → Editor in the left menu.
If you are using a block theme: go to Appearance → Editor → Templates → Product Catalog and edit the template as you wish. You might not want to make any changes, or you might want to tweak a lot. You can read more about the Site Editor in the WordPress.com docs.
If you are using a classic theme: go to Appearance → Customizer → WooCommerce to tweak some settings of the shop page. You can also modify the page directly by going to Pages → Shop (or the page you set as the Shop page) and editing its contents, but keep in mind that in classic themes, WooCommerce adds the product grid automatically, so there are fewer customization options available. If you have Elementor, you might see an Edit with Elementor button at the top left to open its editor.
Given that this is already being tracked on GitHub, I’m going to mark this thread as solved so we can concentrate all communication there. Thanks again for bringing this issue to our attention.
To help us figure out what’s going on, can you tell us in which browsers were you able to reproduce the issue? For what you mention, I understand it has always been on mobile and never on desktop, correct?
Hello again, we have identified the issue and already have a fix in progress. We will release a new version of WooCommerce including the fix next week. Based on that, I will mark this thread as solved. Thanks again for your report!
Hello again, we have identified the issue and already have a fix in progress. We will release a new version of WooCommerce including the fix next week. Based on that, I will mark this thread as solved. Thanks again for your report!
We are currently investigating this issue, but we haven’t been able to reproduce it yet. Could you please share your System Status Report (you can find it from WooCommerce > Status), and the exact page where you encounter the issue, ideally sharing the exact path (ie: /wp-admin/...)?
