Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Zavian Reed

    (@zavian)

    Hi @iexos,

    Thanks for reporting this, and for the clear description. You were right: the line break was being lost on the way to the cart, so “\n” became “n”.

    This is fixed in version 1.2.0, which is now live on WordPress.org. After updating, multi-line answers keep their line breaks in:

    • the cart and checkout
    • the order details in the admin and in customer emails
    • the order item meta returned by the WooCommerce REST API (you’ll get a real “\n”)

    While fixing it we also found that text containing a quote mark (“) or a backslash could cause the customer’s options to be dropped from the order. That is fixed in the same update.

    Please note that orders placed before the update keep the text as it was saved, so they will still show the “n”. Only new orders are affected by the fix.

    If you still see the problem after updating, please let me know which theme you use and whether you’re on the classic or block checkout, and I’ll look into it right away.

    Plugin Support Zavian Reed

    (@zavian)

    Hi @nhillborn,

    Thanks for the detailed request. This is now available in version 1.2.0, which is live on WordPress.org. Please update the plugin to get it.

    Conditional logic rules can now use the product’s variation attributes, so your Hoodie setup works like this:

    1. Open your option set and select the “Placements” (checkbox) field.
    2. Go to the Conditional logic tab and turn it on.
    3. Set it to “Show this field if All of these rules match”.
    4. In the Field dropdown, scroll to “Product attributes” and pick “Custom attribute…”.
    5. Type the attribute name exactly as it is on the product: Style
    6. Set the comparison to “is” and the value to: Full-Zip

    Then select the “Placement” (radio) field and do the same, but:

    • Set it to “Show this field if Any of these rules match”.
    • Add two rules on the Style attribute: “is Kangaroo Pouch” and “is No Pouch”.

    Save, and the product page will switch between the two fields as soon as the customer picks a style. Neither field shows until a style is chosen, and WooCommerce’s “Clear” link hides them again.

    A few notes:

    • Global attributes (Products → Attributes, e.g. Color or Size) appear in the list directly as “Attribute: Color”, with a dropdown of their terms. “Custom attribute…” is for attributes you typed on the product itself, like your Style.
    • Values match by name or slug, and are not case sensitive.
    • The cart also checks these rules on the server. A hidden field is never priced, required fields must be filled, and limits such as “up to 2 placements” are enforced.

    If anything doesn’t behave as you expect with your setup, let me know. A screenshot of the Conditional logic tab helps a lot.

    Plugin Support Zavian Reed

    (@zavian)

    Hi @nhillborn,

    Thanks for the suggestion! We’ve added this to our feature request list for consideration in a future update. We appreciate your feedback!

    Plugin Support Zavian Reed

    (@zavian)

    Hi @iexos,

    Thanks for reporting this issue! We’ve identified the problem with line breaks in multi-line comments and fixed it. The fix will be included in our next release.

    Thanks again for helping us improve the plugin!

    Plugin Support Zavian Reed

    (@zavian)

    Hi @iexos,

    First of all, apologies for the late reply, and thank you for reporting this issue and sharing your workaround. We really appreciate your patience and help in identifying the cause.

    Version 1.1.2 is now available with a fix for this issue! 🎉

    Here’s what we’ve fixed:

    • Hidden fields no longer trigger the browser’s native required validation, and validation is restored when the fields become visible again.
    • Required fields inside hidden Sections are now handled correctly and no longer block the order submission.

    Required fields that are visible will continue to work as expected.

    Please update to version 1.1.2 and remove your custom JavaScript workaround, as it should no longer be necessary.

    Thanks again for bringing this to our attention! If you encounter any further issues, please let us know. We’ll be happy to help.

    Plugin Support Zavian Reed

    (@zavian)

    Hi @thomasr0102 (and @anzette30, @madebynaya),

    Thanks for the detailed report, and sorry for the trouble! We reproduced the issue and fixed it in version 1.1.1.

    Please update the plugin, go to Product Options → Settings, and click Save Settings at the top right to save your changes.

    The CSP eval warning is unrelated to our plugin and likely comes from a browser extension or another plugin.

    I’ll mark this as resolved. Please let us know if the issue persists after updating.

    Plugin Support Zavian Reed

    (@zavian)

    Hi @anzette30,

    Thanks for reporting this, and sorry for the inconvenience! This bug is fixed in version 1.1.1. Please update the plugin, go to Product Options → Settings → Price Display, disable both lines, and click Save Settings at the top right. The changes will now save correctly.

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