WooCommerce Blocks Input field issue

  • Resolved paperclicksdev

    (@paperclicksdev)


    3 months ago

    Hi,

    We are experiencing a bug with our checkout.

    The issue

    We use the Blocks checkout, at the bottom of the page we added the block “input field”.

    This input field is set to “required” in order to place an order. When a customer clicks on the checkbox, we see in the back-end that the input field was answered with “yes”.

    Multiple order came trough where the customer has clicked the checkbox (we verified this with HotJar), but when we look at the order in the back-end we see that they filled it with “no” instead of “yes”.

    We use the Silkypress input field plugin to get this functionality working.

    How to reproduce?

    I haven’t managed to properly reproduce it.

    • Go to the checkout page
    • Click the required checkbox
    • Click the “place order” button
    • Click the required checkbox quickly, before the order has been submitted.
    • The order is now placed in the back-end, but i’m not able to put in a payment.

    When we look at HotJar, we see that the customer just follows the normal steps;

    • Go to the checkout page
    • Click the required checkbox
    • Click the “place order” button

    This results sometimes in the input field being set to “no”

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @paperclicksdev

    Silkypress input field is a third-party plugin, and we don’t provide help & support for 3rd-party plugins or themes as they’re outside our support scope. It would be best to reach out to the plugin developer for further assistance.

    Thanks!

    Thread Starter paperclicksdev

    (@paperclicksdev)

    Ha Shameem,

    Does that mean that the issue is on their end or could it still be a bug in Woo?

    Thanks!

    Hey, @paperclicksdev!

    Since you use the Silkypress input field plugin to get this functionality working, they are the ones that need to check this.

    If you were able to replicate the issue while only having WooCommerce active and no other plugin, then it would be on us to check/fix the issue, but since this is not a WooCommerce feature, but a Silkypress feature, then they are the ones who need to check/fix it.

    I hope this was clarifying. ??

    Please let us know if there’s anything else we can do to help or if you have any questions.

    Have a wonderful day!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Tags