magento2
magento2 copied to clipboard
The shopping cart will be emptied as soon as the forgot password process has been started
Preconditions and environment
- Magento 2.4.7-p1
Steps to reproduce
- add a product to the shopping cart.
- start the "Forgot password" process on the "/customer/account/forgotpassword" page with a customer e-mail address that already exists in the system.
Expected result
The product is still in the shopping cart.
Actual result
The shopping cart has been emptied.
Additional information
Suspected trigger: https://github.com/magento/magento2/commit/7014da918707d3c5ad15ddc59fb85e81e946507c
Proposal: A similar correction as in the model a few years ago. See: https://github.com/magento/magento2/commit/4921f459324328f9b04916f1722e762f98466f5c
Release note
No response
Triage and priority
- [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- [X] 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”.
Hi @sfritzsche. 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:
@magento give me 2.4-develop instance- upcoming 2.4.x release- For more details, review the Magento Contributor Assistant documentation.
- Add a comment to assign the issue:
@magento I am working on this - To learn more about issue processing workflow, refer to the Code Contributions.
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.
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: :point_down:
- [ ] 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: XXXXXlabel to the ticket, indicating the functional areas 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 on2.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.
@magento give me 2.4-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, here is your Magento Instance: https://13e884c2db1a310da91d89f2933c0084.instances-prod.magento-community.engineering Admin access: https://13e884c2db1a310da91d89f2933c0084.instances-prod.magento-community.engineering/admin_5597 Login: 407a653a Password: 84b7fed8a76f
Hi @sfritzsche,
Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the attached video.
Steps to reproduce
- add a product to the shopping cart.
- start the "Forgot password" process on the "/customer/account/forgotpassword" page with a customer e-mail address that already exists in the system.
https://github.com/user-attachments/assets/2e72cb6b-f68c-497e-8cc0-d94ec2f2b6c9
Products were removed from the shopping cart.
Hence confirming the issue.
Thanks.
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12716 is successfully created for this GitHub issue.
:white_check_mark: 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.
@magento give me 2.4-develop instance
Hi @chalov-anton. Thank you for your request. I'm working on Magento instance for you.
Hi @chalov-anton, here is your Magento Instance: https://13e884c2db1a310da91d89f2933c0084.instances-prod.magento-community.engineering Admin access: https://13e884c2db1a310da91d89f2933c0084.instances-prod.magento-community.engineering/admin_b5d9 Login: 7273fce3 Password: b11e33b6c05a
@engcom-Bravo Sorry for the question, but do the pull requests stay until someone is interested in them or do I have to get all tests (incl. Functional Tests EE & Functional Tests B2B which are currently failing due to other work) to run? Unfortunately, I haven't found anything in the documentation on this topic.