Skip to content

#9439 Save region details in order address edit. #9511

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

Closed
wants to merge 6 commits into from
Closed

#9439 Save region details in order address edit. #9511

wants to merge 6 commits into from

Conversation

heyqule
Copy link

@heyqule heyqule commented May 4, 2017

Region is missing in admin order view after order edit. The reason is that the address only save region ID.

This fixes AddressSave controller to save region code and name.

Manual testing scenarios

  1. View pending/processing order in the admin panel
  2. Edit billing or shipping address of the order
  3. Change State/Region field by selecting it from dropdown menu
  4. Save

State/Region should now changed to new region or keep existing region if there is no change.

Region is missing in admin order view after order edit.  The reason is that the address only save region ID.

This fixes AddressSave controller to save region code and name.
@magento-cicd2
Copy link
Contributor

magento-cicd2 commented May 4, 2017

CLA assistant check
All committers have signed the CLA.

@okorshenko
Copy link
Contributor

@heyqule thank you for Pull Request. Could you please please fix class constructor following our backward Compatibility requirement: Adding a constructor parameter

Please, make new class property private

Thank you

heyqule added 3 commits May 22, 2017 11:59
Fix code compatibility according to @okorshenko 

Change variable to private.
Fix constructor based on Backward Compatible Development guide
@heyqule
Copy link
Author

heyqule commented Jun 6, 2017

@okorshenko Hi. Do you have a moment to review the update?

@okorshenko okorshenko self-assigned this Jun 7, 2017
@okorshenko okorshenko added this to the June 2017 milestone Jun 7, 2017
@okorshenko
Copy link
Contributor

Hi @heyqule
Thank you for you contribution. We verified the functionality on latest code from develop branch and this issue does not exists (following Manual testing scenarios). But the issues exists in 2.1-develop branch. If you are interested in this fix, you may analyze how this was done in develop branch and backport the solution to 2.1-develop branch.

Closing this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants