WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 16 months ago

#40212 closed enhancement (wontfix)

Changing your database port in WordPress during installation

Reported by: dickensayieko Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.7.3
Component: Database Keywords:
Focuses: ui Cc:

Description

Hello Core Team,

This is just a suggestion.

What if your database is located on a different port, and need to adjust your connection to connect to it during the WordPress installation process? I know that currently this can be achieved by this code:

define( 'DB_HOST', 'localhost:3306' );

My suggestion is that can we add an option during the installation process to accommodate this? At the stage shown on the attached screenshot.
http://3.1m.yt/_UN_W-7.png

Thanks

Change History (5)

#1 @dd32
4 years ago

  • Keywords close added

Hi @dickensayieko,

This functionality is already supported, although not documented on the installation screen - it even supports MySQL Sockets/pipes using the standard syntax.
https://codex.wordpress.org/Editing_wp-config.php#MySQL_Alternate_Port

Given it's not common to need to change the port (or even hostname) i'm not sure adding a mention of it specifically is needed here - especially as what I'd expect to work (hostname:port) will just work.

#2 @westonruter
4 years ago

  • Component changed from Customize to Database

#3 @swissspidy
4 years ago

What if the database port option only gets added after the first connection attempt was unsuccessful?

#4 @afercia
4 years ago

  • Focuses accessibility removed

Removing the accessibility focus since not strictly related to universal access for everyone :) and to keep this ticket out from the Trac accessibility report.

#5 @pento
16 months ago

  • Keywords close removed
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

I'm inclined to agree that adding extra UI to the install process for a database port is not necessary, given that adding the port to the host field works.

Note: See TracTickets for help on using tickets.