#53871 closed defect (bug) (duplicate)
Database errors on installation
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 5.8 |
Component: | Database | Keywords: | |
Focuses: | Cc: |
Description
The following errors are logged in PHP error log during installation:
[04-Aug-2021 08:33:47 UTC] WordPress database error Unknown column 'wp_' in 'field list' for query SELECT wp_ [04-Aug-2021 08:33:47 UTC] WordPress database error Incorrect table name '' for query INSERT INTO `` (`option_name`, `option_value`, `autoload`) VALUES ('nonce_key', 'vg_!Z2{kS%>2}8HYQ2$tJBgx.%vQy2*LxtqCa7=>JQpQ6wOs4vpZjOajJl^$<QbW', 'no') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`) made by wp_print_scripts, wp_scripts, WP_Scripts->__construct, WP_Scripts->init, do_action_ref_array('wp_default_scripts'), WP_Hook->do_action, WP_Hook->apply_filters, wp_default_scripts, wp_create_nonce, wp_hash, wp_salt, update_site_option, update_network_option, add_network_option, add_option [04-Aug-2021 08:33:47 UTC] WordPress database error Incorrect table name '' for query INSERT INTO `` (`option_name`, `option_value`, `autoload`) VALUES ('nonce_salt', '3 g|1IXHd?6yz/5&jJ<%^~LGMF-O5dGSEy.*4;=;|P~[]A&I(J!SL2v:9Vc{t?*m', 'no') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`) made by wp_print_scripts, wp_scripts, WP_Scripts->__construct, WP_Scripts->init, do_action_ref_array('wp_default_scripts'), WP_Hook->do_action, WP_Hook->apply_filters, wp_default_scripts, wp_create_nonce, wp_hash, wp_salt, update_site_option, update_network_option, add_network_option, add_option
I was able to confirm this several times on 2 different servers. Those errors appear in the log after DB credentials screen when you get to "All right, sparky! You’ve made it through this part of the installation." screen.
Change History (3)
Note: See
TracTickets for help on using
tickets.
Thanks for your report.
This has since been fixed already in #53830