Closed (outdated)
Project:
Commerce Core
Version:
7.x-1.x-dev
Component:
Customer
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Feb 2014 at 20:35 UTC
Updated:
8 Nov 2018 at 15:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
marktheshark commentedComment #2
jcl324I can confirm this happens on KS 2.6 as well.
Comment #3
marktheshark commentedComment #4
makokis commentedsame issue here using
Commerce Kickstart (commerce_kickstart-7.x-2.12) and
Commerce Addressbook 7.x-2.0-rc7
see attached
Comment #5
marktheshark commentedHate to bump, but this is still a problem.
It would be useful to have this issue acknowledged by the maintainers of Commerce Address Book.
Comment #6
lsolesen commented@marktheshark Would you be able to create a Behat test showing this problem?
Comment #7
lsolesen commentedI can confirm that it seems that the shipping information is copied again, when using this Behat test:
https://github.com/lsolesen/commerce_kickstart/blob/addressbook/tests/be...
However, I am not certain whether this is expected behavior?
Comment #8
lsolesen commentedRelated to #1958698: Erratic "Address on file" behavior during checkout - Address selection not respected - (Dis)appearing addresses
Comment #9
marktheshark commentedHello, I would expect that there should be some hash of address fields that helps detect identical information and not create identical entries if the address hash matches.
That being said, this occurs even if you select an existing address from your address list.
Comment #10
Infinitee commentedI am having this problem with the latest CK... 7.x-2.15
Go to checkout and the address fields are empty even with an address on file.
Try to apply "Address on file" and nothing happens.
Fill out BILLING INFORMATION form and it adds another address to "Address on file" list.
Comment #11
Infinitee commentedComment #12
lsolesen commentedComment #13
mglamanThis is a Drupal Commerce bug, which may have been fixed recently.
Comment #14
sjmobley commentedThis issue has been resolved by a recent update to the Addressfield module.