Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use DB_CHARSET utf8mb4 by default #230

Closed
ideadapt opened this issue Jan 17, 2016 · 1 comment
Closed

Use DB_CHARSET utf8mb4 by default #230

ideadapt opened this issue Jan 17, 2016 · 1 comment

Comments

@ideadapt
Copy link

Since April 2015, WordPress uses utf8mb4 by default. It would be nice if you do so as well in config/application.php.
When I got this error using wp import export.sql:

ERROR 1366 (HY000) at line 215: Incorrect string value: '\xF0\x9F\x8C\xAE" ...' for column 'option_value' at row 1

It cost me some time to realize, that my wp-config was wrong.

Changing
define('DB_CHARSET', 'utf8');
to
define('DB_CHARSET', 'utf8mb4');
resolved it.

@swalkinshaw
Copy link
Member

@ideadapt thanks, updated.

seafarer added a commit to seafarer/bedrock that referenced this issue Mar 22, 2016
* 'master' of github.com:roots/bedrock:
  Add wp-password-bcrypt plugin for secure passwords
  1.5.4 CHANGELOG
  Fix roots#241 - Use https for wpackagist.org
  Bump WordPress to 4.4.2
  Bump composer/installers
  1.5.1 CHANGELOG
  Use oscarotero/env instead of `getenv`
  Update CHANGELOG.md
  In Bash, environment variable is always a string. Because of the way this constant is checked in WP ( defined('DISABLE_WP_CRON') && DISABLE_WP_CRON ), DISABLE_WP_CRON=false would resolve to true.
  Fix roots#230 - Set default `DB_CHARSET` to `utf8mb4`
  Bump WordPress to 4.4.1
  Bump WordPress to 4.4
  Update README.md
  used nested WP_HOME in WP_SITEURL

# Conflicts:
#	composer.json
#	composer.lock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants