-
Notifications
You must be signed in to change notification settings - Fork 35
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
customer address country selection issue in admin panel #28
Comments
I've noticed this when creating an order in admin for alternative store views other than GB - when you click 'get available shipping methods' it defaults the shipping address back to UK. For now I've removed all of the layout xml updates for admin except tag_settings_index.xml - this does mean that it can't be used but its better than not having shipping rates when creating admin orders! |
I know this extension is defunct now, but I've been in contact with Loqate about this issue - it occurs on the front end too - so customers selecting a country other than the default (in this case UK) will be reverted to UK in the payment step. This is what they said in support:
So even though this advice doesn't necessarily apply to the correct extension, it could well be an issue in the Loqate account as opposed to Magento. |
Following feedback from support. We found this issue was resolved by removing "field mode" "Country" from the country field mapping for offending service. In our case we removed the Country Field Mode from country field mapping for all services. "You can adjust this behaviour by disabling the "Country" field mode in your installation under the Mappings tab." |
We are facing an issue where country dropdown defaults to United Kingdom when editing a customer address in admin panel, this is not ideal when editing non UK addresses, e.g. if a customer already has an address in Ireland and we want to edit this address to change street then we would like the country drop down to not switch to UK from Ireland.
Module: pcapredict/tag 2.0.6
Magento: 2.2.4
The text was updated successfully, but these errors were encountered: