Closed
Description
Preconditions (*)
- Magento Open Source 2.3.4 to 2.4.1
- Configure Customer street lines to 3 or more lines
- No additional module or configuration is required
Steps to reproduce (*)
- Go to Customer configuration in admin, and set the number of street lines to 3 or more (
customer/address/street_lines) - In the frontend, proceed to checkout and add a new address. When adding a new address in the checkout, leave blank street lines in the middle. I.e: Populate line 1 with
Line 1string, and line 3 withLine 3string. - After the order is placed and the address is saved, try to edit this address or see this address in the database (table
customer_address_entity).
Expected result (*)
- It's expected to see the line 1 and 3 populated in the frontend when going to customer's adress book (/customer/address).
- It's expected to see the value
Line 1⏎⏎Line 3in the database
Actual result (*)
- The value we inserted in the address line 3 is displayed as line 2 when editing the address
- In
customer_address_entity.streetcolumn we seeLine 1⏎Line 3.
Note that doesn't happen if you manually insert the address in customer area (instead of inserting it during the checkout).
Additional Information
Quote from #27847 (comment)
I don't remember problems in the frontend, except when editing the address.
The main problem is that it breaks integrations that relies on the correct line. For instance, we use line 4 as Neighborhood in many stores in Brazil, but we faced integration issues when it's saved in line 3. It also breaks payments integrations(and payment methods) that requires neighborhood for placing an order. In those cases, registered customers can't place an order with an existing address.
These are just a few cases.
Metadata
Metadata
Assignees
Labels
Gate 2 Passed. Manual verification of the issue description passedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 1 Passed. Automatic verification of issue format passedGate 4. Acknowledged. Issue is added to backlog and ready for developmentMay be fixed according to the position in the backlog.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branchAffects non-critical data or functionality and does not force users to employ a workaround.Has been reviewed and prioritized during Triage with Product Managers
Type
Projects
Milestone
Relationships
Participants
Activity
m2-assistant commentedon Apr 13, 2020
Hi @r-martins. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance- upcoming 2.4.x releaseFor more details, please, review the Magento Contributor Assistant documentation.
@r-martins do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
r-martins commentedon Apr 13, 2020
@magento give me 2.4-develop instance
magento-engcom-team commentedon Apr 13, 2020
Hi @r-martins. Thank you for your request. I'm working on Magento 2.4-develop instance for you
magento-engcom-team commentedon Apr 13, 2020
Hi @r-martins, here is your Magento instance.
Admin access: https://i-27847-2-4-develop.instances.magento-community.engineering/admin_cf28
Login:
215c7447Password:b4652bc4c4ccInstance will be terminated in up to 3 hours.
r-martins commentedon Apr 13, 2020
@magento give me 2.3.4 instance
magento-engcom-team commentedon Apr 13, 2020
Hi @r-martins. Thank you for your request. I'm working on Magento 2.3.4 instance for you
magento-engcom-team commentedon Apr 13, 2020
Hi @r-martins, here is your Magento instance.
Admin access: https://i-27847-2-3-4.instances.magento-community.engineering/admin_e1fa
Login:
f8da86f9Password:8287f1b7f570Instance will be terminated in up to 3 hours.
r-martins commentedon Apr 14, 2020
I could reproduce the error both in 2.3.4 and 2.4-develop instances when adding address in checkout process.
m2-assistant commentedon Apr 14, 2020
Hi @krishprakash. 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).
Details
If the issue has a valid description, the labelIssue: Format is validwill be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is validappears.2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Descriptionlabel to the issue by yourself.3. Add
Component: XXXXXlabel(s) to the ticket, indicating the components it may be related to.4. Verify that the issue is reproducible on
2.4-developbranchDetails
- Add the comment@magento give me 2.4-develop instanceto deploy test instance on Magento infrastructure.- If the issue is reproducible on
2.4-developbranch, please, add the labelReproduced 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: Confirmedonce verification is complete.6. Make sure that automatic system confirms that report has been added to the backlog.
25 remaining items
r-martins commentedon Jan 15, 2021
I was able to test the Pull Request #28126 on Magento 2.4.1 and it seems it does fix this issue. I hope someone from Magento could notice the importance of this issue.
r-martins commentedon Jan 27, 2022
🎂 Happy birthday to this old and persistent bug! I hope someone takes care of you one day.
ZIPITRO commentedon Mar 17, 2022
Anyone can move this issue to the drawing table please?
engcom-Bravo commentedon Jun 26, 2024
Hi @r-martins,
Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4-develop instance and the issue is no more reproducible.Kindly refer the attached video.
Screen.Recording.2024-06-26.at.09.55.08.mov
We are able to to see the line 1 and 3 populated in the frontend when going to customer's adress book
Hence we are closing this issue.
Thanks.