Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

Two "The provided postcode / ZIP is not valid" error message are displayed. #8387

Closed
fetenlakhal opened this issue Feb 4, 2023 · 2 comments · Fixed by #8390
Closed

Two "The provided postcode / ZIP is not valid" error message are displayed. #8387

fetenlakhal opened this issue Feb 4, 2023 · 2 comments · Fixed by #8390
Labels
type: bug The issue/PR concerns a confirmed bug.

Comments

@fetenlakhal
Copy link

fetenlakhal commented Feb 4, 2023

Describe the bug

5927922-zd / 40342701-hc

If you add a wrong zip code, two "The provided postcode / ZIP is not valid" error messages are displayed. If you correct the zip code, the first one disappears; The second is stuck. This is happening with the new version 9.5.0.

To reproduce

Steps to reproduce the behavior:

  1. Add the latest version of WooCommerce Blocks on your website
  2. Add the check-out block on your check-out page.
  3. Add a product to the cart and go to checkout
  4. Change country to Poland for example with the zip code 40-837.
  5. Change country to United Kingdom.
  6. You will see two "The provided postcode / ZIP is not valid" error messages.
  7. Change the zip code to E14 9AJ
  8. The first "The provided postcode / ZIP is not valid" error message is stuck.

Expected behavior

Only one "The provided postcode / ZIP is not valid" error message is displayed and disappears after correcting the zip code.

Screenshots

Please check this Gif: d.pr/i/IkNwW4

Environment

WordPress (please complete the following information):

  • WordPress version: 6.1.1
  • WooCommerce version: 7.1.0
  • WooCommerce Blocks version: 9.5.0
  • Site language: English

Additional context

The user also reported that the order summary was not updated after that, but I can't reproduce that.

@fetenlakhal fetenlakhal added the type: bug The issue/PR concerns a confirmed bug. label Feb 4, 2023
@gameDNA-Helix
Copy link

+1

@senadir
Copy link
Member

senadir commented Feb 6, 2023

Thank you for reporting this @taftina, I managed to reproduce it and will push a fix.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug The issue/PR concerns a confirmed bug.
Projects
None yet
3 participants