Conversation
Prefill the email field with 'admin@localhost.com' instead of leaving it empty. For pre-existing sites without a stored email, fetch it from WordPress via 'wp user get <username> --field=user_email'. Make the field mandatory with always-on validation. Remove the help text comment about defaults.
📊 Performance Test ResultsComparing 60442fa vs trunk site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
gcsecsey
left a comment
There was a problem hiding this comment.
Thanks @bcotrim for improving this! 🙌 This is looking good to me, and tests well. Unfortunately I didn't have a site from earlier, but I confirm the validation works great for a new site:
CleanShot.2026-02-27.at.15.26.39.mp4
epeicher
left a comment
There was a problem hiding this comment.
Thanks @bcotrim! I have tested it, and I see the email validation when creating the site and when deleting the email from an existing (or new) site. LGTM!
One small detail that can be tacked as a follow-up is that the validation message displayed when editing a site and deleting the email is hidden from the viewport and the user needs to scroll down. Initially, I saw the red outline but didn't see the message, then I realised I needed to scroll, please see the video below
CleanShot.2026-02-27.at.17.49.57.mp4
This is such a minor detail, but I believe addressing it will enhance the validation UX.
Related issues
Related to #2527 (Add support for Blueprints login)
Proposed Changes
admin@localhost.cominstead of leaving it emptywp user get <username> --field=user_emailwhen opening site settings (uses the stored admin username or defaults toadmin)Testing Instructions
For new sites:
admin@localhost.comFor pre-existing sites:
Pre-merge Checklist