#45840 closed defect (bug) (invalid)
After New WordPress Setup Getting Query Error
Reported by: | vikashsaharan | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 5.0.2 |
Component: | Upgrade/Install | Keywords: | |
Focuses: | Cc: |
Description
After WP setup getting all query print on this link wp-admin/install.php?step=2
WordPress database error: [Table 'wp_users' already exists]
CREATE TABLE wp_users ( ID bigint(20) unsigned NOT NULL auto_increment, user_login varchar(60) NOT NULL default , user_pass varchar(255) NOT NULL default , user_nicename varchar(50) NOT NULL default , user_email varchar(100) NOT NULL default , user_url varchar(100) NOT NULL default , user_registered datetime NOT NULL default '0000-00-00 00:00:00', user_activation_key varchar(255) NOT NULL default , user_status int(11) NOT NULL default '0', display_name varchar(250) NOT NULL default , PRIMARY KEY (ID), KEY user_login_key (user_login), KEY user_nicename (user_nicename), KEY user_email (user_email) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci
Welcome to WordPress core trac.
This is where we follow up on confirmed bugs in WordPress core.
To me, this doesn't look like a bug (yet). You just need to make sure that if you support more than one WordPress installation from one and the same database, then each site MUST use it's own prefixes.
If you need more help with your situation, then please post in https://wordpress.org/support/ instead.
PS! If you later, after troubleshooting would reach to the conclusion that this actually IS a bug, then you can reopen the ticket and add more details about what one needs to do in order to replicate the bug. (The first step in confirming a bug is to be able to make the same error occur on a different installation.)