WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#16229 closed defect (bug) (invalid)

Setting empty table prefix on Setup Config not respected

Reported by: knutsp Owned by:
Milestone: Priority: normal
Severity: minor Version: 3.0.4
Component: Upgrade/Install Keywords:
Focuses: Cc:

Description

The default table prefix is "wp_" and this is shown on "setup-config.php?step=1". If you remove this, make it empty, and presses Submit, when you inspect your created wp-config.php, the table prefix is set to "wp_".

To be able to make an install from scratch with no table prefix one has to manually edit wp-config.php. No big problem, but WordPress should respect one's wishes, and no prefix should be perfectly ok.

See line 160, 161 in wp-admin/setup-config.php

Change History (3)

comment:2 mdawaffe3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

An empty prefix has never been supported. WordPress requires a non-empty prefix.

It'd be nicer if the installer showed an error instead of changing things behind your back, but no prefix is not ok.

comment:3 nacin3 years ago

Also of note why we require a non-empty prefix, prefixes are used in usermeta, and if there's no prefix on the meta key, then it'll be considered global. So having no prefix is definitely buggy.

Note: See TracTickets for help on using tickets.