Interactivity API: Variation options disabled

  • Resolved Vania

    (@twvania)


    6 months, 4 weeks ago

    This issue is critical and currently blocks purchases on production stores.

    There is already an open issue for this problem: #63430, but it has been open for over a month without a fix, and the problem affects real stores using the woocommerce/add-to-cart-with-options block.

    I can confirm that the issue is broader than described.

    If an attribute (including taxonomy-based attributes) contains non-ASCII characters, for example:

    “Ilość” (Polish), all variation options become disabled.
    Options (e.g., “10 ml”, “150 ml”) are rendered but cannot be selected.

    From debugging, isOptionDisabled is triggered for all options.

    Steps to reproduce:

    1. Create a variable product
    2. Use an attribute (taxonomy) named “Ilość”
    3. Add variation values (e.g., “10 ml”, “150 ml”)
    4. Generate variations and set prices
    5. Open product page using woocommerce/add-to-cart-with-options block

    Actual result:
    All variation options are disabled (unclickable): https://prnt.sc/UkZAgS0KLXaP

    Expected result:
    Options should be selectable

    Note:

    This is not just about spaces — any diacritics (e.g., Polish characters like “ść”) trigger the issue.
    If possible, this needs prioritization, as it directly prevents purchases.

    Best Regards,
    Vania

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Vania

    (@twvania)

    6 months, 4 weeks ago

    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

    shahzeen(woo-hc)

    (@shahzeenfarooq)

    6 months, 4 weeks ago

    Hi there!

    Thank you for bringing this to our attention. There is already an existing issue report that occurs when the attribute title and slug are not identical. Currently, you are facing a similar issue when using specific characters like “ść” in the attribute title. In this case, the slug appears as simple characters like “sc”, which makes the title different from the slug, as shown in this screenshot: https://go.screenpal.com/watch/cOevosnTw6g

    Here is the bug report for the attribute title and different slug issue: https://github.com/woocommerce/woocommerce/issues/63794

    I would suggest submitting a comment on this thread so you can receive updates directly from our developers.

    I’m glad you were able to find a workaround. Please note that the issue only appears with the Add to Cart + Options (Beta) block. If you replace it with the standard Add to Cart + Options block, the issue does not occur; however, the variable will appear in a dropdown.

    Thank you for your understanding and cooperation.

    Plugin Contributor Albert Juhé Lluveras

    (@aljullu)

    6 months, 3 weeks ago

    Thanks for opening this issue and confirming the bug, folks! A fix for it has been included in WC 10.6.2.

    If you encounter any issues after updating, please feel free to answer this thread or open a new one. Thanks in advance!

    LovingBro (woo-hc)

    (@lovingbro)

    6 months, 3 weeks ago

    Hi @twvania,

    I can see this was a critical issue impacting purchases, so I wanted to follow up now that the thread has been marked as resolved.

    Following @aljullu’s update about the fix being included in WooCommerce 10.6.2, have you had a chance to update and confirm everything is working as expected on your end?

    If you are all set now, that is great to hear. If you still need any help or notice anything unusual, feel free to get back to us here and we will gladly continue looking into it with you.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Interactivity API: Variation options disabled’ is closed to new replies.