Title: encoding after upgrading
Last modified: August 18, 2016

---

# encoding after upgrading

 *  Resolved [jland](https://wordpress.org/support/users/jland/)
 * (@jland)
 * [18 years, 11 months ago](https://wordpress.org/support/topic/encoding-after-upgrading/)
 * When I upgraded wp to 2.2, my Japanese text got scrambled.
    I went back and copy/
   pasted the original Japanese into the post… but the text is still showing up 
   as ??? I made new posts with Japanese text, and it’s still ???
 * What happened…? And how do I fix this?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [moshu](https://wordpress.org/support/users/moshu/)
 * (@moshu)
 * [18 years, 11 months ago](https://wordpress.org/support/topic/encoding-after-upgrading/#post-580374)
 * This might help:
    [http://codex.wordpress.org/Editing_wp-config.php#Database_character_set](http://codex.wordpress.org/Editing_wp-config.php#Database_character_set)
 *  Thread Starter [jland](https://wordpress.org/support/users/jland/)
 * (@jland)
 * [18 years, 11 months ago](https://wordpress.org/support/topic/encoding-after-upgrading/#post-580428)
 * I read over that, and I checked my wp-config.php.
    it says define(‘DB_CHARSET’,‘
   utf8’); exactly like that documentation said.
 *  [moshu](https://wordpress.org/support/users/moshu/)
 * (@moshu)
 * [18 years, 11 months ago](https://wordpress.org/support/topic/encoding-after-upgrading/#post-580430)
 * The documentation says exactly **NOT TO HAVE IF IT IS AN UPGRADE**…
    There really
   must be a problem how they teach people to read! Quote:
 * > Warning for those performing upgrades: 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 problems — as Ryan Boren says, “**your queries will go boom!**“
 *  Thread Starter [jland](https://wordpress.org/support/users/jland/)
 * (@jland)
 * [18 years, 11 months ago](https://wordpress.org/support/topic/encoding-after-upgrading/#post-580434)
 * oh haha
    I read the “do not add” and I figured I wasn’t adding anything so I 
   skipped over that.
 * so are you saying I should delete
 *     ```
       define('DB_CHARSET', 'utf8');
       define('DB_COLLATE', '');
       ```
   
 * that’s in my wp-config.php?
 * I want some confirmation in case my wp goes kaboom…

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘encoding after upgrading’ is closed to new replies.

## Tags

 * [encoding](https://wordpress.org/support/topic-tag/encoding/)
 * [upgrade](https://wordpress.org/support/topic-tag/upgrade/)

 * In: [Installing WordPress](https://wordpress.org/support/forum/installation/)
 * 4 replies
 * 2 participants
 * Last reply from: [jland](https://wordpress.org/support/users/jland/)
 * Last activity: [18 years, 11 months ago](https://wordpress.org/support/topic/encoding-after-upgrading/#post-580434)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics