Contact Form: email recipient field does not correctly handle other users editing a page with a form #40108
Labels
[Block] Contact Form
Form block (also see Contact Form label)
[Feature] Contact Form
[Feature] Forms Blocks
Blocks designed to streamline user input and engagement, such as contact, newsletter sign-ups, etc.
[Platform] Atomic
[Platform] Simple
[Plugin] Jetpack
Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/
[Pri] Low
[Status] Needs Design
Triaged
[Type] Bug
When a feature is broken and / or not performing as intended
Impacted plugin
Jetpack
Quick summary
Jetpack's Contact Form sends an email notification for each form to the post author by default. That can be changed for each contact form individually, by setting a custom
to
value.In the block editor, the recipient email field displays the current user's email address by default, and when saving an updated form, the
to
value is not updated if the field value matches the default value. It consequently creates an issue when someone other than the post author wants to update that value to their own email address ; their change is not saved because the value they entered matches the default email field value (the current email address).The only workaround in this scenario is to enter 2 email addresses, since the field value then does not match the default.
Steps to reproduce
Note
Start with a site where you have 2 registered users: the main admin (email address
[email protected]
) and an editor (email address[email protected]
).[email protected]
.[email protected]
.[email protected]
.A clear and concise description of what you expected to happen.
Since the form settings indicated
[email protected]
when I hit save, I would expect that to be the new recipient email address value from now on.What actually happened
If I refresh the page, and then view the code editor view of the block editor, I do not see any
to
block attribute saved for the contact form block. The form still uses the default recipient email address, the page author email address,[email protected]
.Impact
Some (< 50%)
Available workarounds?
No but the platform is still usable
If the above answer is "Yes...", outline the workaround.
No response
Platform (Simple and/or Atomic)
Simple, Atomic, Self-hosted
Logs or notes
This was originally reported and discussed here: p9F6qB-gom-p2
The text was updated successfully, but these errors were encountered: