Opened 9 years ago
Closed 9 years ago
#36238 closed defect (bug) (invalid)
uft8mb4 upgrade fails if using db.php drop-in
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 4.2 |
| Component: | Database | Keywords: | |
| Focuses: | Cc: |
Description
Hyperdb is a popular database class that supports replication, failover, load balancing, and partitioning. Many other database drop-ins are based on hyperdb. In the core On the upgrade to the database in WordPress 4.2/4.3 if does a check to see if the database is capable of supporting uft8mb4. However these changes are not reflected in hyperdb. This means that when the upgrade is trigger it fails gracefully and the upgrade doesn't happen. Because there is no feedback that upgrade failed, it seems like the upgrade was successful.
In production we had the Twitter auto-embed issue occur in WP 4.4.1. All db drop-ins need to be updated to support utf8mb4.
Here is an example of an updated hyperdb with utf8mb4 support - https://github.com/johnjamesjacoby/ludicrousdb
First report: https://wordpress.org/support/topic/utf8mb4-wp-42-not-supported?replies=1
This appears to be specific to the HyperDB plugin, which is managed by Automattic rather than WordPress.org, so the plugin support forum is the correct place for this report.