#19970 closed defect (bug) (fixed)
Self-created config file allows invalid table prefix
Reported by: | rmarks | Owned by: | rmarks |
---|---|---|---|
Milestone: | 3.4 | Priority: | normal |
Severity: | normal | Version: | 3.3.1 |
Component: | Upgrade/Install | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
It's possible to manually create a wp-config.php file with an empty table prefix. This will create the tables and possible work okay as a standalone install, but this causes problems in Multisite.
Attachments (2)
Change History (10)
#3
follow-up:
↓ 5
@
13 years ago
So we don't tank existing installs, this should only prevent it on install.php.
Good idea though.
#5
in reply to:
↑ 3
@
13 years ago
- Component changed from General to Upgrade/Install
- Milestone changed from Awaiting Review to 3.4
Replying to nacin:
So we don't tank existing installs, this should only prevent it on install.php.
19970.2.diff is the patch for install.php
. Also adds some whitespace as per coding standards.
Replying to kurtpayne:
Should the prefix also be run through
strtolower()
? Related #19748
I guess we should remove strtolower()
in #19748.
Note: See
TracTickets for help on using
tickets.
Attached is a patch that will abort the install if there is an empty table prefix.