Open braders opened 3 years ago
Hi @braders. 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 release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
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, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-Oscar. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:
Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.:white_check_mark: Confirmed by @engcom-Oscar
Thank you for verifying the issue. Based on the provided information internal tickets MC-42053
were created
Issue Available: @engcom-Oscar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
@magento I am working on it
I have resolved reference message hello@example.com. Go to Store > Configuration > General > Contacts > Email options then enter your preferred email in the send email to field
Hi @braders ,
Thanks for your reporting and collaboration. We have verified the issue in latest 2.4-develop instance and it is an improvement so we will mark ticket as feature request.
Steps to reproduce 1.Disable Contact us from admin area (Configuration -> General -> Contacts -> Enable Contact Us)
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
The hello@example.com email address should be easily updatable. You should not need to change the configuration for other areas of functionality (contact form) as a prerequisite for updating this field.
It may be that the password reset error message should actually be using a different email address field.
Actual result (*)
You are unable to update the reference to hello@example.com unless the contact form functionality is disabled.
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.