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.

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

Allowed Countries does not work correctly #38181

Open
1 of 5 tasks
zhovnirigor opened this issue Nov 15, 2023 · 11 comments · May be fixed by #38182
Open
1 of 5 tasks

Allowed Countries does not work correctly #38181

zhovnirigor opened this issue Nov 15, 2023 · 11 comments · May be fixed by #38182
Labels
Area: Account Component: Customer Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: PR in progress Reported on 2.4.6-p3 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@zhovnirigor
Copy link

zhovnirigor commented Nov 15, 2023

Preconditions and environment

  1. Magento version 2.4.6-p3
  2. Share Customer Accounts (customer/account_share/scope) = Global
  3. Allowed countries (general/country/allow) in the default website (for instance, British Website) are set to set X (for instance, United Kingdom only).
  4. Allowed countries (general/country/allow) in any other website (for instance, Irish Website) are set to set Y (for instance, Ireland only).
  5. Create a customer in the Store View that does not belong not to default website (for instance, create it in any store that belongs to Irish Website).
  6. Assign some address to the previously created customer with the country that is allowed not only not in the default website (for instance, with the country Ireland).

Steps to reproduce

First case:

  1. Do a PUT request to the /rest/V1/customers/[customer_id], where [customer_id] is the entity_id of the customer created on the 5th step of preconditions.

Another case:

  1. In the admin panel, edit the customer created on the 5th step of preconditions.
  2. Go to the tab Addresses
  3. Click Edit on the address created on the 6th step of preconditions.

Expected result

First case:

PUT request is executed without any errors

Another case:

Country field is present and contains all the available values (so United Kingdom and Ireland, for example).

Actual result

First case:

An error occurred 'Invalid value of "IE" provided for the countryId field.'

Another case:

Country field is not present at all.

Additional information

Fixed in #38182

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • 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”.
Copy link

m2-assistant bot commented Nov 15, 2023

Hi @zhovnirigor. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

@zhovnirigor
Copy link
Author

@magento give me 2.4-develop instance

Copy link

Hi @zhovnirigor. Thank you for your request. I'm working on Magento instance for you.

Copy link

@engcom-Bravo engcom-Bravo self-assigned this Nov 15, 2023
Copy link

m2-assistant bot commented Nov 15, 2023

Hi @engcom-Bravo. 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: 👇

  • 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- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - 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.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.6-p3 Indicates original Magento version for the Issue report. label Nov 15, 2023
@m2-community-project m2-community-project bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Nov 15, 2023
@zhovnirigor zhovnirigor removed their assignment Nov 15, 2023
@m2-community-project m2-community-project bot added this to Pull Request In Progress in High Priority Backlog Nov 15, 2023
@m2-community-project m2-community-project bot removed this from Ready for Confirmation in Issue Confirmation and Triage Board Nov 15, 2023
@zhovnirigor zhovnirigor removed their assignment Nov 22, 2023
@engcom-Bravo
Copy link
Contributor

@magento give me 2.4-develop instance

Copy link

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

Copy link

@engcom-Bravo
Copy link
Contributor

Hi @zhovnirigor,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

First case:

  • Do a PUT request to the /rest/V1/customers/[customer_id], where [customer_id] is the entity_id of the customer created on the 5th step of preconditions.

Another case:

  • In the admin panel, edit the customer created on the 5th step of preconditions.
  • Go to the tab Addresses
  • Click Edit on the address created on the 6th step of preconditions

john-mag-Customers-Customers-Magento-Admin

https-7731cb2cb3d426ed681353fa21ec77a2-instances-prod-magento-community-engineering-rest-default-V1-customers-2-My-Workspace

First case:

An error occurred 'Invalid value of "IE" provided for the countryId field.'

Another case:

Country field is not present at all.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Area: Account Component: Customer Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed and removed Issue: ready for confirmation labels Dec 12, 2023
@github-jira-sync-bot
Copy link

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

Copy link

m2-assistant bot commented Dec 12, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Account Component: Customer Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: PR in progress Reported on 2.4.6-p3 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
High Priority Backlog
  
Pull Request In Progress
Development

Successfully merging a pull request may close this issue.

3 participants