Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support Phone Numbers for Singapore not being validated - starting with 800, 805, 806, 807, 808, 809 #10373

Open
sverleis opened this issue Feb 14, 2025 · 0 comments
Open

Support Phone Numbers for Singapore not being validated - starting with 800, 805, 806, 807, 808, 809 #10373

sverleis opened this issue Feb 14, 2025 · 0 comments
Labels
component: settings Issues related to Settings focus: account lifecycle priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability type: bug The issue is a confirmed bug.

Comments

@sverleis
Copy link

sverleis commented Feb 14, 2025 •
edited
Loading

Describe the bug

When a merchant from Singapore [+65] is looking to add a Support phone number via Payments > Settings, any number starting with 800 or 805 - 809 is rejected.

To Reproduce

  1. Go to Payments > Settings > Transactions
  2. Add a support phone number, select Singapore as the country (+65)
  3. Add the rest of the number, starting with 800, 805, 806, 807, 808 or 809.
  4. The components-notice is-error is shown, stating "Please enter a valid phone number."

Screenshots

Image

Expected behavior

Numbers should validate correctly

Desktop (please complete the following information):

  • OS: MacOS 15.3
  • Browser: Chrome 133.0.6943.54
  • WooPayments 8.9.1

Additional context

Noted on #9402369-zen
@sverleis sverleis added the type: bug The issue is a confirmed bug. label Feb 14, 2025
@aheckler aheckler added needs triage Manually put issue into triage process. component: settings Issues related to Settings focus: account lifecycle labels Feb 14, 2025
@anu-rock anu-rock added priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability and removed needs triage Manually put issue into triage process. labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: settings Issues related to Settings focus: account lifecycle priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability type: bug The issue is a confirmed bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@anu-rock @aheckler @sverleis