magento2 icon indicating copy to clipboard operation
magento2 copied to clipboard

Telephone field in customer account does not validate

Open marctbb opened this issue 1 year ago • 20 comments

Preconditions and environment

Magento 2 versions tested:

  • 2.4.6-p4 (with the default Blank theme).
  • 2.4.7 (also tested with the default Blank theme).

Configuration:

  • Stores > Configuration > Customers > Customer Configuration > Show Telephone: Set to Required.

Issue observed in both environments and themes.

Steps to reproduce

  1. Go to My Account as a logged-in customer.
  2. Attempt to Add or Edit the telephone field under account details.
  3. Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
  4. Save the changes.

Expected result

  • The telephone field in the My Account section should validate input to ensure it is a valid phone number (e.g., digits only, proper phone format).
  • Invalid input should trigger an error message and prevent saving.

Actual result

  • The telephone field in My Account allows invalid input (e.g., text or symbols) without validation.
  • In the checkout, when retrieving customer details from the account, the invalid phone number causes errors during the shipping process.
  • For example, UPS shipping fails to process the order due to incorrect phone number format.

Additional information

  • Video evidence of the issue is attached for reference.
  • The issue occurs regardless of the Magento version (tested on 2.4.6-p4 and 2.4.7) or theme used (Blank theme).
  • This inconsistency between the My Account section and Checkout makes it critical, as incorrect phone numbers lead to shipping failures.

https://github.com/user-attachments/assets/10689ac7-e900-4111-a35a-e1bde0c7e217

Release note

No response

Triage and priority

  • [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

marctbb avatar Nov 22 '24 11:11 marctbb

Hi @marctbb. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

m2-assistant[bot] avatar Nov 22 '24 11:11 m2-assistant[bot]

Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

  • [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • [ ] 5. Add label Issue: Confirmed once verification is complete.
  • [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

m2-assistant[bot] avatar Nov 22 '24 11:11 m2-assistant[bot]

Hi @marctbb ,

Thanks for your reporting and collaboration. We have verified the issue in Latest 2.4 develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce Stores > Configuration > Customers > Customer Configuration > Show Telephone: Set to Required. image

  1. Go to My Account as a logged-in customer.
  2. Attempt to Add or Edit the telephone field under account details.
  3. Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
  4. Save the changes. Observe Error displays when user fill invalid phone number image Invalid phone number error

Can you please re-verify and confirm if you are still facing the issue. Thanks.

engcom-Delta avatar Nov 22 '24 11:11 engcom-Delta

Hi,

Thank you for your response and for verifying the issue.

I have re-tested this scenario using a freshly installed Magento 2.4.7-p3 instance, and I can confirm that the issue still occurs in this version. I have attached a video recording demonstrating the exact steps and the error encountered when entering invalid input in the telephone field.

Key details of the environment:

  1. Magento Version: 2.4.7-p3
  2. Environment: Fresh installation, no third-party extensions or customizations

Steps followed are identical to those mentioned in the ticket. The error persists when saving invalid phone numbers like abc123 or !@# in the customer account details. It does not trigger the expected validation message.

  • Attached Evidence:

  • Video of the issue reproduction in my environment

Could you kindly verify this on a Magento 2.4.7-p3 environment or provide any additional steps for us to align?

Looking forward to your feedback.

Best regards,

marctbb avatar Nov 25 '24 14:11 marctbb

Hi @marctbb ,

Thanks for your reporting and collaboration. We have verified the issue in 2.4.7-p3 instance and the issue is reproducible. Kindly refer the screenshots.

Steps to reproduce

  1. Go to My Account as a logged-in customer.
  2. Attempt to Add or Edit the telephone field under account details.
  3. Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
  4. Save the changes.
  5. Observe Error does not display when user fill invalid phone number image

Thanks.

engcom-Delta avatar Nov 26 '24 12:11 engcom-Delta

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-13418 is successfully created for this GitHub issue.

github-jira-sync-bot avatar Nov 26 '24 12:11 github-jira-sync-bot

:white_check_mark: Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

m2-assistant[bot] avatar Nov 26 '24 12:11 m2-assistant[bot]

:x: You don't have permission to export this issue.

github-jira-sync-bot avatar Nov 26 '24 12:11 github-jira-sync-bot

@magento I'm working on this

magentoabu avatar Nov 29 '24 07:11 magentoabu

Hello @engcom-Delta,

As per discussion in the community triage call please re-verify this issue in 2.4.8-beta1 also.

Thanks

engcom-Hotel avatar Dec 03 '24 11:12 engcom-Hotel

Hi @marctbb ,

We have verified the issue in 2.4.8-beta 1 instance and latest 2.4 develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce

  1. Go to My Account as a logged-in customer.
  2. Attempt to Add or Edit the telephone field under account details.
  3. Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
  4. Save the changes.
  5. Observe Error displays when user fill invalid phone number image

Issue is fixed in latest version 2.4.8-beta1 and latest 2.4 develop instance, We suggest you to please verify in latest version and confirm if you are still facing the issue. Removing the confirmed label as issue is only replicable in 2.4.7-p3 instance. Thanks.

engcom-Delta avatar Dec 04 '24 08:12 engcom-Delta

Hi, As we mentioned earlier, the issue has been confirmed in version 2.4.7, which is the version we are currently using. A fix is necessary as I will not be upgrading to a beta version or 2.4.8 at this moment, since it involves significant changes to my Magento instance.

I kindly insist that the issue be resolved for version 2.4.7.

Thank you for your understanding.

Best regards,

marctbb avatar Dec 04 '24 16:12 marctbb

Hello, is there any update on whether there is a solution or a workaround?

Thanks

marctbb avatar Dec 17 '24 15:12 marctbb

Hi @marctbb,

We are in discussion with PO regarding patch, till then we are moving the issue to "On Hold"

Thanks.

engcom-Delta avatar Dec 18 '24 10:12 engcom-Delta

Hi @marctbb ,

Thanks for your reporting and collaboration. We have verified the issue in 2.4.7-p3 instance & 2.4-develop branch and the issue is reproducible. Kindly refer the screenshots. Hence Confirming the issue.

Steps to reproduce 2.4.7-p3 Instance

  1. Go to My Account as a logged-in customer.
  2. Attempt to Add or Edit the telephone field under account details.
  3. Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
  4. Save the changes.
  5. Observe Error does not display when user fill invalid phone number

Image

2.4-develop branch -

  1. Go to My Account as logged-in customer.
  2. Attempt to add or edit the telephone field under account details.
  3. Enter invalid input, e.g. alphabets in telephone field.
  4. Save changes.
  5. Observe user is able to enter alphabets in telephone field.

Image

Thanks.

engcom-Delta avatar Jan 20 '25 10:01 engcom-Delta

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-13418

github-jira-sync-bot avatar Jan 20 '25 10:01 github-jira-sync-bot

@magento run all tests

ajay2108 avatar Feb 28 '25 16:02 ajay2108

@magento run all tests

ajay2108 avatar Mar 06 '25 11:03 ajay2108

Hello @ajay2108,

Just want clarify you, the command which you have tried to run above will work only on the PRs, not in issues. As I can see you have created this PR https://github.com/magento/magento2/pull/39688, please run this command there to run all the tests.

Thanks

engcom-Hotel avatar Mar 07 '25 06:03 engcom-Hotel

Hello, any update about this?

Thank you

marctbb avatar Jun 16 '25 14:06 marctbb