wp-config differences in 2.2 — should I add DB_COLLATE or avoid it?
My wp-config looks like this
define('DB_NAME', 'my_name'); // The name of the database (DG also have 'my_name') define('DB_USER', 'my_name'); // Your MySQL username define('DB_PASSWORD', 'my_password'); // ...and password define('DB_HOST', 'localhost'); // 99% chance you won't need to change this value
wp-config-sample from WP 2.2 looks similar but it adds this:
define('DB_CHARSET', 'utf8'); define('DB_COLLATE', '');
When I upgraded from 2.0.x to 2.2, I followed the Upgrade Instructions in the Codex, which tells me to copy my old wp-config. Therefore the DB_CHARSET and DB_COLLATE are not in my wp-config.
Should I add those 2 lines? Where does it tell me to do this, in the documentation or Codex? Is it safe to just add those 2 lines, and save the file?
Yes, I have read the following pages in the Codex, and they are either Rough Drafts, or tell me NOT to add the above lines:
But I’m still wondering if I need those lines, because I am having a lot of character encoding issues, and also my feed doesn’t work and the validation error mentions the utf8.
- The topic ‘wp-config differences in 2.2 — should I add DB_COLLATE or avoid it?’ is closed to new replies.