WP upgrade is failing after update to WP 6.4.2 due to HyperDB
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Reproduce a WordPress 6.4.2 core, plugin, theme, or translation update with HyperDB enabled, comparing behavior with db-config.php unchanged and HyperDB removed. Start at wordpress/wp-includes/class-wpdb.php:4158 and trace the calls through wordpress/wp-includes/update.php:78 and the upgrader stack; done means WP Admin updates no longer fail with a null mysqli value.
Written by the indexing model from the issue text.
Description
We are using HyperDB for long time and it has been mostly smooth experience so far. However, after upgrading to WordPress 6.4.2 we are expriencing database issues when running WP updates of core, plugins, themes and/or translations via WP Admin.
Our db-config.php did not change and only way of upgrading now is to temporarily switch HyperDB off by removing it from wordpress root dir.
Maybe somebody else also run into this issue and might have any insights?
Thank you.
Error example
PHP Fatal error: Uncaught TypeError: mysqli_get_server_info(): Argument #1 ($mysql) must be of type mysqli, null given in wordpress/wp-includes/class-wpdb.php:4158
Stack trace:
#0 wordpress/wp-includes/class-wpdb.php(4158): mysqli_get_server_info(NULL)
#1 wordpress/wp-includes/update.php(78): wpdb->db_server_info()
#2 wordpress/wp-admin/includes/class-wp-upgrader.php(844): wp_version_check(Array)
#3 wordpress/wp-admin/includes/class-plugin-upgrader.php(392): WP_Upgrader->run(Array)
#4 wordpress/wp-admin/update.php(51): Plugin_Upgrader->bulk_upgrade(Array)
#5 {main}
thrown in wordpress/wp-includes/class-wpdb.php on line 4158
- Dominant language
- PHP
- Stars
- 150
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Automattic/HyperDB
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Automattic/HyperDB#191 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Automattic/HyperDB#160 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
Automattic/HyperDB#141 · 2 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Automattic/HyperDB#139 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Automattic/HyperDB#138 · 1 comment ·
All issues in Automattic/HyperDB
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·