WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#2910 closed enhancement (duplicate)

Allow user to choose login name and password during setup

Reported by: ketsugi Owned by: darkfate
Milestone: Priority: normal
Severity: normal Version: 2.0.4
Component: Administration Keywords: bg|has-patch
Focuses: Cc:

Description

When running install.php, the default user's login name is set to "admin" and the password to a random string. Why not allow the user to type a login name and choose a password right at the beginning, negating the necessity for the user to immediately login and change the password. This would also mean that there will be fewer (eventually) Wordpress installs out there with an "admin" account with admin privileges.

Attachments (2)

install.php.diff (3.2 KB) - added by darkfate 8 years ago.
allow user the select username
install.php.2.diff (3.2 KB) - added by darkfate 8 years ago.
forgot to add a semicolon

Download all attachments as: .zip

Change History (8)

comment:1 ketsugi8 years ago

...Or you could ignore everything I said about the password, since it's already covered in #2870, and let this ticket be just about the login name.

darkfate8 years ago

allow user the select username

comment:2 darkfate8 years ago

  • Keywords bg|has-patch added
  • Milestone set to 2.0.4
  • Owner changed from anonymous to darkfate
  • Status changed from new to assigned
  • Type changed from defect to enhancement

comment:3 darkfate8 years ago

I figured it would be safer to keep the password randomized. It produces a strong password and some people's passwords tend to not be that secure. This gives wordpress security by default.

comment:4 darkfate8 years ago

I guess we want to sanitize the username to be safe. I would use something like:

if(!eregi("^([0-9 a-z])+$", $admin_username)) {};

Or should it use the functions in registration_functions.php like on lines 38 and 39.

darkfate8 years ago

forgot to add a semicolon

comment:5 darkfate8 years ago

  • Resolution set to duplicate
  • Status changed from assigned to closed

See bug #2870 for this patch plus some added stuff.

comment:6 anonymous7 years ago

  • Milestone 2.0.4 deleted

Milestone 2.0.4 deleted

Note: See TracTickets for help on using tickets.