ok, fixed with next update.
Nope, this is not fixed yet, I’m getting the same error still in 3.0.4…
If you go to /wp-admin/admin.php?page=backwpupsettings and click the Information tab, you’ll see that Blog charset is set to ‘DB_CHARSET’, which is the root of the problem.
To fix this, you need to set the DB_CHARSET environment variable in your wp-config.php, with the rest of your database settings. For example:
define(‘DB_CHARSET’, ‘utf8’);
Be careful with that…
WARNING: Those performing new installations: There usuallly should be no reason to change the default value of DB_CHARSET. If your blog needs a different character set, please read Character Sets and Collations MySQL Supports for valid DB_CHARSET values.
WARNING: Those performing upgrades (especially blogs that existed before 2.2): If DB_CHARSET and DB_COLLATE do not exist in your wp-config.php file, DO NOT add either definition to your wp-config.php file unless you read and understand Converting Database Character Sets. Adding DB_CHARSET and DB_COLLATE to the wp-config.php file, for an existing blog, can cause major problems.
Source: http://codex.ww.wp.xz.cn/Editing_wp-config.php#Database_character_set
Gabe
(@gabrielwhite)
Same issue here, and I’m using a wp-config.php that doesn’t include a definition of the charset (per the post of @chrispix above).
I’m getting backup files, but they don’t include the database dump.
Gabe
