Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jetpack Form block: Ability to autocomplete email address of logged-in users #29924

Open
Gustavo-Hilario opened this issue Apr 1, 2023 · 5 comments
Labels
[Block] Contact Form Form block (also see Contact Form label) Customer Report Issues or PRs that were reported via Happiness. aka "Happiness Request", or "User Report" [Feature] Contact Form [Pri] Low [Status] Stale Triaged [Type] Bug When a feature is broken and / or not performing as intended [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it

Comments

@Gustavo-Hilario
Copy link

What

Add the ability to pre-fill input fields on the Jetpack Form block with the logged-in user information, like their email address.

Why

The user on 6088200-zen have some forms that should be filled out by their site members. My understanding is they need to do that routinely, so having the option to pre-fill as many inputs as possible would be helpful.

How

I see this is already implemented in the "Subscribe" block. Maybe we could replicate the same to the Form block.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2023

Support References

This comment is automatically generated. Please do not edit it.

  • 6088200-zen

@cuemarie
Copy link

cuemarie commented Apr 4, 2023

📌 ACTIONS

  • Feature request kept

@cuemarie cuemarie added [Pri] Normal [Block] Contact Form Form block (also see Contact Form label) Triaged labels Apr 4, 2023
@matticbot matticbot added the Customer Report Issues or PRs that were reported via Happiness. aka "Happiness Request", or "User Report" label Apr 4, 2023
@cuemarie cuemarie transferred this issue from Automattic/wp-calypso Apr 4, 2023
@jeherve
Copy link
Member

jeherve commented Apr 5, 2023

This may be a regression, as it used to work that way on WordPress.com simple (but not on WoA or self-hosted, see #694). Behaviour may be different for the contact form shortcode vs. the form block.

@jeherve jeherve added [Type] Bug When a feature is broken and / or not performing as intended [Pri] Low and removed [Type] Feature Request [Pri] Normal labels Apr 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 3, 2023

This issue has been marked as stale. This happened because:

  • It has been inactive for the past 6 months.
  • It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, `[Type] Feature Request`, `[Type] Enhancement`, `[Type] Janitorial`, `Good For Community`, `[Type] Good First Bug`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

@simison simison added [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Type] Bug When a feature is broken and / or not performing as intended and removed [Type] Bug When a feature is broken and / or not performing as intended labels Jan 2, 2025
@enejb
Copy link
Member

enejb commented Jan 17, 2025

This behaviour can be triggered by using the add_filter( 'jetpack_auto_fill_logged_in_user', '__return_true' ); filter.

It would be great to document it.

cc: @simison Should we add it as a checkbox on the form settings or on the field level?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Contact Form Form block (also see Contact Form label) Customer Report Issues or PRs that were reported via Happiness. aka "Happiness Request", or "User Report" [Feature] Contact Form [Pri] Low [Status] Stale Triaged [Type] Bug When a feature is broken and / or not performing as intended [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it
Projects
None yet
Development

No branches or pull requests

6 participants