[wp-trac] [WordPress Trac] #32212: Multisite Sites Cannot Create Database tables in 4.2.1 fresh clean install
WordPress Trac
noreply at wordpress.org
Thu Apr 30 17:11:45 UTC 2015
#32212: Multisite Sites Cannot Create Database tables in 4.2.1 fresh clean install
--------------------------------+------------------------------
Reporter: reidbusi | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Networks and Sites | Version: 4.2.1
Severity: normal | Resolution:
Keywords: reporter-feedback | Focuses: multisite
--------------------------------+------------------------------
Comment (by reidbusi):
'''Can you check to see if mysqli is supported in your PHP
configuration?:'''
MysqlI Support enabled
Client API library version 5.5.40-36.1
'''What MySQL version are you running?:'''
5.5.40-36.1 - Percona Server (GPL), Release 36.1, Revision 707
- (My host apparently changed to Percona without notice. Supposedly it is
a drop-in replacement for MySQL, but I have never heard of it.)
'''What are the DB_CHARSET and DB_COLLATE values set to in wp-
config.php?:'''
{{{
define('DB_CHARSET', 'utf8mb4');
define('DB_COLLATE', '');
}}}
- (as set by the installer, have not modified)
'''What charset and collation are set as default in your MySQL
configuration?
'''
As I am not root, I am not sure. But when I create a new database from the
cPanel account the collation is utf8_unicode_ci.
This is what phpMyAdmin tells me:
{{{
character set client utf8
(Session value) utf8mb4
character set connection utf8
(Session value) utf8mb4
character set database utf8
character set filesystem binary
character set results utf8
(Session value) utf8mb4
character set server utf8
character set system utf8
character sets dir /usr/share/percona-server/charsets/
collation connection utf8_unicode_ci
(Session value) utf8mb4_unicode_ci
collation database utf8_unicode_ci
collation server utf8_unicode_ci
}}}
'''Do have error logs on which queries failed? I'm guessing it's because
of the collation, but an explicit MySQL error would be great.'''
I currently do not, I did from my last attempt... oh wait I do have those
saved... here is an example:
{{{
[30-Apr-2015 13:56:07 UTC] WordPress database error COLLATION
'utf8_general_ci' is not valid for CHARACTER SET 'utf8mb4' for query
CREATE TABLE wpmu_5_terms (
term_id bigint(20) unsigned NOT NULL auto_increment,
name varchar(200) NOT NULL default '',
slug varchar(200) NOT NULL default '',
term_group bigint(10) NOT NULL default 0,
PRIMARY KEY (term_id),
KEY slug (slug(191)),
KEY name (name(191))
) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8_general_ci made by
wpmu_activate_signup, wpmu_create_blog, install_blog,
make_db_current_silent, dbDelta
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/32212#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list