Critical Issue: Variable Products broken after WooCommerce update (Outdated Temp

*** UPDATE ON THIS TICKET – PLEASE READ BEFORE CHECKING THE SITE ***

I am writing to update this ticket with critical technical information. The “Add to Cart” button on my variable products is currently working ONLY because I applied a temporary custom JavaScript patch (workaround).

Please do NOT close this ticket assuming the issue is resolved. The root cause lies within the WoodMart theme templates being incompatible with WooCommerce 10.5+, specifically regarding how the “disabled” attribute is handled on the add-to-cart button.

HERE IS THE TECHNICAL DIAGNOSIS:

1. The Issue: Without my custom JS patch, the “Add to Cart” button remains disabled/unclickable even after a variation is selected.
2. The Logs: I ran a console diagnostic script. The WooCommerce event found_variation FIRES correctly, and the variation JSON data IS present. The theme receives the data but fails to update the UI state of the button (it fails to remove the disabled attribute and class).
3. The Environment: This happens mainly for non-logged-in users, suggesting a conflict between cached assets and the way the outdated WoodMart variable.php template initializes the form state in the new WooCommerce version.
4. The Temporary Fix: To prevent sales loss, I had to inject the following jQuery script to force the button to unlock:

jQuery(‘.variations_form’).on(‘found_variation’, function(event, variation) {
var $btn = jQuery(‘.single_add_to_cart_button’);
$btn.removeAttr(‘disabled’).removeClass(‘disabled’); // Forcing removal of the block

// Ensuring ID is passed
var $hiddenId = jQuery(‘.variation_id’);
if ($hiddenId.length > 0 && variation.variation_id) {
$hiddenId.val(variation.variation_id);
}
});

REQUEST:
I cannot keep this custom script forever as it is not a clean solution. I need WoodMart to release an official update or patch for the woodmart/woocommerce/single-product/add-to-cart/variable.php (and related JS files) to natively support the new button state handling in WooCommerce 10.5.

Please investigate why the native theme script fails to unlock the button upon the found_variation event and provide a permanent fix.

Thank you.

I am writing to provide a final update on this ticket.

After extensive testing and debugging, we identified that the root cause was indeed a regression in the WooCommerce Core (v10.5 branch) regarding how the “Add to Cart” button disabled state was handled for variable products.

This has now been officially acknowledged and addressed by the WooCommerce team in Pull Request #63194:
https://github.com/woocommerce/woocommerce/pull/63194

Our Findings & Solution:
During the downtime, the only way to keep the store operational was to implement a custom JavaScript patch via functions.php. This patch manually intercepted the found_variation event to remove the disabled attribute that WooCommerce was incorrectly persisting.

Next Steps:
I am now proceeding to update WooCommerce to the latest patch version that includes this fix. Once updated, I will remove my temporary custom code from functions.php.

I wanted to share this with you so you are aware that this was not a plugin conflict (as previously suggested), but a Core behavior change that affected themes relying on specific JS execution orders.

You may consider this ticket resolved.

Best Regards