Opened 5 years ago
Closed 4 years ago
#4382 closed enhancement (fixed)
Profile username validation on meetup application form
Reported by: | hlashbrooke | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | WordCamp Site & Plugins | Keywords: | needs-patch good-first-bug |
Cc: |
Description
We often receive meetup applications that contain invalid or non-existent WordPress.org usernames. These all come from the application form here: https://central.wordcamp.org/meetup-organizer-application/
It would be great if we could add some validation on that form that checks if the username exists (simply checking if the profile URL exists should be sufficient) and then, if it does not, prevents submission and directs the applicant to create a profile first.
Change History (4)
This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.
4 years ago
#4
@
4 years ago
- Resolution set to fixed
- Status changed from assigned to closed
I think this was fixed by https://github.com/WordPress/wordcamp.org/commit/92c0c72da94ba0ea9d93665ab2261455e81c4abe#diff-31d28ac8b089034ed639e52e6231e897 awhile back, but please reopen if not.
I ran into this a related problem today on the applicant's Slack username. At the very least, I'd like to suggest the username not have the @ symbol as a prefix.
For the original scenaio that @hlashbrooke reported, would we just look for the HTTP response code after accessing the user's profile? If it's a 200, allow the form to be submitted. If it's a 404, prevent the form from being submitted and show an message requesting they check their username or register for an account.