Vania

I was able to confirm that the issue is caused by character normalization.

As a quick test, I added the following workaround:

add_filter( 'woocommerce_attribute_label', function( $label, $name, $product ) {
	return remove_accents( $label );
}, 10, 3 );

After applying this, variation options become selectable again and everything works as expected.

However, this is not a valid solution, since it modifies the displayed attribute labels (e.g., “Ilość” → “Ilosc”), which is not acceptable for production stores.

This confirms that the root cause is the mismatch between normalized (slugified) attribute names and human-readable labels when non-ASCII characters are involved.

Best Regards,
Vania

Reported here: https://github.com/woocommerce/woocommerce/issues/62227

Hi Frank,
Thank you for the response!

I understand that the New Product Editor is currently paused, but the issue I reported is still a real, reproducible bug in the version that is currently shipped inside WooCommerce. Even if the feature is paused for future development, the existing implementation should not crash or throw JavaScript errors — especially since users may still have the New Product Editor enabled.

A few important clarifications:

1. WordPress 6.9 RC4 is officially available via the WordPress Beta Tester plugin.
   It’s not an unofficial build — RC4 was released publicly and can be installed by anyone testing the upcoming version.
2. WordPress 6.9 stable is being released today, which means WooCommerce will need compatibility very soon — and currently the Full Editor inside the Description field crashes immediately.
3. Even if the editor is paused for redesign, the current code should fail gracefully, not break the entire Description UI with a JS exception.

Because of this, I believe the issue should still be tracked as a bug in the existing implementation, so the team can patch or disable the problematic code path before it affects all users.

Thanks!

https://pastebin.com/DE3gy1t6

And error:

[02-Dec-2025 10:45:13 UTC] PHP Fatal error:  Uncaught Automattic\WooCommerce\GoogleListingsAndAds\Exception\InvalidValue: Invalid coupon ID: 59 in .../wp-content/plugins/google-listings-and-ads/src/Exception/InvalidValue.php:95
Stack trace:
#0 .../wp-content/plugins/google-listings-and-ads/src/Coupon/CouponHelper.php(207): Automattic\WooCommerce\GoogleListingsAndAds\Exception\InvalidValue::not_valid_coupon_id(59)
#1 .../wp-content/plugins/google-listings-and-ads/src/Admin/MetaBox/CouponChannelVisibilityMetaBox.php(138): Automattic\WooCommerce\GoogleListingsAndAds\Coupon\CouponHelper->get_wc_coupon(59)
#2 .../wp-content/plugins/google-listings-and-ads/src/Admin/MetaBox/AbstractMetaBox.php(105): Automattic\WooCommerce\GoogleListingsAndAds\Admin\MetaBox\CouponChannelVisibilityMetaBox->get_view_context(Object(WP_Post), Array)
#3 .../wp-admin/includes/template.php(1456): Automattic\WooCommerce\GoogleListingsAndAds\Admin\MetaBox\AbstractMetaBox->handle_callback(Object(WP_Post), Array)
#4 .../wp-admin/edit-form-advanced.php(714): do_meta_boxes(Object(WP_Screen), 'side', Object(WP_Post))
#5 .../wp-admin/post-new.php(75): require('/home/klient.dh...')
#6 {main}
  thrown in .../wp-content/plugins/google-listings-and-ads/src/Exception/InvalidValue.php on line 95

Screen: https://prnt.sc/Gokzh_2iB8D_

• This reply was modified 5 months, 1 week ago by Vania.

Hi Marin,

thank you for the quick response and for releasing the fix so fast!
I’ve just updated to version 2.5.7 and can confirm that everything works correctly now — the price comparison behaves exactly as expected with our 4-decimal setup.

Really appreciate your work and the quick turnaround.
Great job!

Best regards,
Vania

It’s not a problem, it’s just information 😉

Thank you, the new version does not have this error.

Best Regards,
Vania