Issue with the Gutenberg fields

  • euzebiobatista

    (@euzebiobatista)


    1 day, 16 hours ago

    Hello Support Team, hope you’re doing well.

    We received a ticket from a customer stating that the First Name and Last Name fields on the checkout form (blocks/Gutenberg) are not working.

    I investigated further and noticed that:
    When I copy the filled name and delete it, the input event (or something similar) does not trigger the ‘update-customer‘ event. I know these fields are required and must be filled in, but this causes some confusion and UX issues. Specifically, they revert to their previous state whenever an event like a shipping method change or a coupon insertion occurs—suddenly, fields that should be empty reappear with the old data.

    Which leads me to think: if these fields are already required, there shouldn’t be an issue with the ‘update-customer’ event being triggered with empty fields. Upon form submission, both the frontend and backend will validate the information and alert the user accordingly, preventing unexpected behavior.

    Perhaps this issue is also happening with other fields.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    20 hours, 59 minutes ago

    Hi @euzebiobatista!

    I understand the issue you’re describing with the First Name and Last Name fields in the Checkout Block. In particular, when the fields are cleared, the expected update-customer event does not appear to be triggered, and the previous values can reappear after actions such as changing the shipping method or applying a coupon. I understand how this could lead to confusing behavior for customers.

    To help us investigate this further, could you please confirm:

    • Were these fields working correctly before, and if so, when did you first notice the issue?
    • Were any changes made to the site before the issue started, such as a WooCommerce/plugin update, theme change, customization, or checkout configuration change?
    • Could you create a short video demonstrating the issue? This would help us see exactly what happens when the fields are cleared and when another checkout action causes the previous values to reappear.
    • Please also share your site URL so we can better understand the checkout setup.
    • Please provide the WooCommerce System Status Report from WooCommerce → Status → Get system report → Copy for support.
    • If there are any relevant Fatal Error Logs, please share those as well from WooCommerce → Status → Logs.

    With these details, we’ll be able to better understand whether the behavior is related to a recent change, a plugin/theme conflict, or the Checkout Block itself.

    For easier sharing, you can paste both reports into Pastebin and send us the links. When creating the Pastebin entries, please make sure the “Burn after read” option is turned off, so the reports remain available for us to review.

    Once we have these details, we can investigate the cause of the error and advise you on the appropriate next steps.

    Thread Starter euzebiobatista

    (@euzebiobatista)

    14 hours, 24 minutes ago

    Hello @shahzeenfarooq ,
    I am from Brazil, so please excuse my English.

    • Were these fields working correctly before, and if so, when did you first notice the issue?
      I discovered this bug a few days ago, but I believe it has already been there for a while.

    • Were any changes made to the site before the issue started, such as a WooCommerce/plugin update, theme change, customization, or checkout configuration change?
      Initially, I thought it could be a theme issue or a conflict with a plugin from the company I work for. However, I created a completely fresh environment from scratch using only WordPress + WooCommerce, and the bug occurs there as well.

    • Could you create a short video demonstrating the issue? This would help us see exactly what happens when the fields are cleared and when another checkout action causes the previous values to reappear.
      Sure! Here is the video link: https://www.linknacional.com.br/assets/suporte/player/suporte_6a6b690f27c91_4cddc7d7
      In the video, I use the browser’s Inspect tool (Network tab) to show that the batch request with the update-customer action is not being called. It is only called when both fields are filled out.

    • Please also share your site URL so we can better understand the checkout setup.
      I can share a URL if needed. Keep in mind that our clients’ sites use some of our custom checkout plugins, but as I mentioned above (with the fresh install), the bug occurs regardless of the plugins installed.

    • Please provide the WooCommerce System Status Report from WooCommerce → Status → Get system report → Copy for support.
      I can send you the report if you want, but I don’t believe it’s necessary. As shown in the video, I didn’t even need to submit the form to reproduce the bug, so it shouldn’t generate any system logs or warnings.

    • If there are any relevant Fatal Error Logs, please share those as well from WooCommerce → Status → Logs.
      No, it doesn’t generate any fatal errors. As I said above, I don’t think it generates any logs at all. The problem seems to be a condition directly in the form’s JS/TSX file, which is preventing the batch request from being sent when a field is left empty.
Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.