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. We dont know if the problem is within Woo or Silkypress

    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 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Diana Burduja

    (@diana_burduja)

    Hello @paperclicksdev,

    I cannot replicate the issue on my test website. Would you create me a test product with 0€ as price on your website, so I can see the issue live?

    Are all the orders on your website with “Ik kan alle vragen uit de inventarisatie mondzorg met ja beantwoorden.” field answered as “no”, or only some of the orders? If only some of the orders, could you find a pattern between the orders, for example “they all use the same payment method” or “they all use only a certain browser”?

    One possible cause could be that the checkbox is set outside the checkout form, after the “Afrekenen” button. Would you mind moving the checkbox above the “Afrekenen” button (before or after the “Terms and Conditions”, as you wish) and watch out if the checkbox’s value is correctly registered in future orders?

    Thread Starter paperclicksdev

    (@paperclicksdev)

    Hi @diana_burduja,

    ?cannot replicate the issue on my test website. Would you create me a test product with 0€ as price on your website, so I can see the issue live?

    I have created a new product with 0 as price.You will find it here: https://whiteteethforever.eu/product/test/

    Good to know the payment options will error because the price is 0.

    Are all the orders on your website with “Ik kan alle vragen uit de inventarisatie mondzorg met ja beantwoorden.” field answered as “no”, or only some of the orders? If only some of the orders, could you find a pattern between the orders, for example “they all use the same payment method” or “they all use only a certain browser”?

    Most of them are answered with “Yes”, but only some with “no”. The most recent one we have recorded on HotJar, you can see there that the checkbox was checked in the normal manner. But afterwards in the order it still says “no”.

    It’s with different payment methods, browsers and devices. There is no pattern to be recognized.

    One possible cause could be that the checkbox is set outside the checkout form, after the “Afrekenen” button. Would you mind moving the checkbox above the “Afrekenen” button (before or after the “Terms and Conditions”, as you wish) and watch out if the checkbox’s value is correctly registered in future orders?

    As requested, we have moved the checkbox to be inside the checkout form. I dont know if this will solve the issue since i cant properly reproduce it.

    Plugin Author Diana Burduja

    (@diana_burduja)

    The test orders with the 0€ product seem to register correctly the checkbox’s value.

    I was hoping you’d find a pattern in the orders, so that we could somehow replicate the issue. But, as we cannot replicate it, I’m afraid I got stuck for the moment.

    Thread Starter paperclicksdev

    (@paperclicksdev)

    Hi,

    That’s unfortunate. is there any way to manually edit the data?

    What do you need to be able to look further in to this?

    Plugin Author Diana Burduja

    (@diana_burduja)

    You can always manually edit the data by opening the WooCommerce order, then scroll down to the “Custom Fields” section and change the value for the input field.

    If you don’t see the “Custom Fields” section, then it could be hidden. You can show it again by clicking the “Screen Options” button on the top right side of the page (right under the dark admin bar at the top of the page), then tick the checkbox next to the “Custom Fields” label.

    Generally the bugs that show up only sometimes, without a reliable way of replicating, can hardly be solved, because changing anything in the code or in the settings will not tell us if it solves the bug or not. If you find a reliable way to replicate the bug, then let me know.

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