Make WordPress Core

Opened 14 years ago

Last modified 5 years ago

#13103 assigned defect (bug)

"Unknown character set" during install into database reports successful install.

Reported by: mecu's profile MECU Owned by: barrykooij's profile barrykooij
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Database Keywords: has-patch needs-refresh
Focuses: Cc:


During editing of the wp-config.php, I changed

define('DB_CHARSET', 'utf8');


define('DB_CHARSET', 'utf8_general_ci');

Which I thought was valid.

After clicking "Install Wordpress" I got a page full of:

WordPress database error: [Unknown character set: 'utf8_general_ci']

And at the bottom, "Success" with a login prompt, but nothing was actually created in the database.

I think WP shouldn't report a successful install if the user happened to accidentally change this value (or another) during install as it would cause confusion.

I used a svn checked out version of WP on 2010-04-24 on my local computer using PHP5 and apache2, but I think this is really a problem since 2.6 (or when the current install system was implemented).

Attachments (2)

install.php.patch (1.2 KB) - added by barrykooij 12 years ago.
13103.patch (816 bytes) - added by SergeyBiryukov 12 years ago.

Download all attachments as: .zip

Change History (16)

#1 @dd32
14 years ago

  • Keywords needs-patch added; install error database removed
  • Milestone changed from Unassigned to Future Release

utf8_general_ci is not a valid charset (Character Set), What it is, Is a valid collation

You can set the Collation via the constant DB_COLLATE, but the charset should stay as 'utf8'.

The installer should reconise failed SQL queries however, I'm not sure why it doesnt already.

Future Release pending patch.

#2 @hakre
14 years ago

Needs review if it still applies for trunk.

#3 @barrykooij
12 years ago

  • Owner set to barrykooij
  • Status changed from new to assigned

#4 @barrykooij
12 years ago

  • Keywords has-patch added; needs-patch removed

This is my first patch so please tell me if I did anything wrong in Trac :)

#5 @SergeyBiryukov
12 years ago

  • Component changed from General to Upgrade/Install
  • Keywords needs-refresh added
  • Priority changed from lowest to normal
  • Severity changed from trivial to normal

#6 @barrykooij
12 years ago

I will add a new patch next week, thanks for your feedback.

#7 @SergeyBiryukov
12 years ago

__('The charset \''.DB_CHARSET.'\' set in wp-config.php, is not available in your database.')

This is not localizable, sprintf() should be used instead:

#8 @barrykooij
12 years ago

New patch uploaded.

Installer is now checking Database collation before the user can fill in the form, because he will not be able to install WordPress if the collation is wrong anyway.

12 years ago


#9 @SergeyBiryukov
12 years ago

  • Keywords needs-refresh removed

#10 @SergeyBiryukov
12 years ago

  • Milestone changed from Future Release to 3.5

#11 @MikeHansenMe
11 years ago

Tested 13103.patch and it prevents me from starting the install as expected with a bad DB_CHARSET. Looks good for me.

#12 @nacin
11 years ago

  • Component changed from Upgrade/Install to Database
  • Milestone changed from 3.5 to Future Release

I'd like to test this some more. A false negative could result in people being unable to install WordPress, which is not good.

#13 @pento
11 years ago

A couple of thoughts:

SHOW CHARACTER SET was added in 5.0.3 - do we want a version check in wpdb::has_cap() for that?

I suspect it may be possible to configure a MySQL server such that SHOW CHARACTER SET performs a case sensitive search, even though the related server variables are case insensitive. Ie, the following query fails:


The query would allow for that as:

$wpdb->prepare( 'SHOW CHARACTER SET WHERE LOWER( Charset ) = LOWER( %s )', DB_CHARSET )

#14 @chriscct7
9 years ago

  • Keywords needs-refresh added
Note: See TracTickets for help on using tickets.