WordPress.org

Ready to get started?Download WordPress

Forums

Upgrade to 2.2 - new config file caused — punctuation read errors (2 posts)

  1. protechs
    Member
    Posted 7 years ago #

    Keeping everything upgraded, so went from 2.1.3 to 2.2 and just happened to notice the two new lines on the config.php file.

    I just did a delete and then total clean install of version 2.2 and got all those ascii replacements throughout most posts which used many different kinds of punctuation.
    It did not matter what theme. I upgraded another blog a few hours earlier and no problems. However...

    This time I had USED THE BRAND-NEW CONFIG.PHP FILE (first new one I've ever seen and I almost didn't look at it).

    As soon as I read another thread I caught this phrase:

    Or any other editor, which supports UTF-8,

    and remembered seeing that line on the New config.php file.

    I deleted the new and put back in the old and everything was perfect again. This is the first ever problem I've had with a WordPress install (script-wise) in about 40 installs and upgrades since May 2004.

    This makes me really nervous because those new changes were put there for a reason, but it causes a major problem. I work on 4 servers with all mySQL and phpmyadmin current versions. Two other upgrades were fine because I didn't notice the config.php change. If I use the new one, you get ascii replacements.

    $64 question. WHY? Did I miss a bulletin that we are to make SQL/Database changes first before upgrade?? Will this lead to other problems in future upgrades that need those two lines in there??

    Thank you very much!!

    <?php
    // ** MySQL settings ** //
    define('WP_CACHE', true); //Added by WP-Cache Manager
    define('DB_NAME', 'account_name'); // The name of the database
    define('DB_USER', 'account_user'); // Your MySQL username
    define('DB_PASSWORD', 'secretword'); // ...and password
    define('DB_HOST', 'localhost'); // 99% chance you won't need to change this value
    define('DB_CHARSET', 'utf8');
    define('DB_COLLATE', '');

    // You can have multiple installations in one database if you give each a unique prefix
    $table_prefix = 'wp_'; // Only numbers, letters, and underscores please!

    // Change this to localize WordPress. A corresponding MO file for the
    // chosen language must be installed to wp-content/languages.
    // For example, install de.mo to wp-content/languages and set WPLANG to 'de'
    // to enable German language support.
    define ('WPLANG', '');

    /* That's all, stop editing! Happy blogging. */

    define('ABSPATH', dirname(__FILE__).'/');
    require_once(ABSPATH.'wp-settings.php');
    ?>

  2. MichaelH
    Member
    Posted 7 years ago #

    If you upgrade you shouldn't add the DB_CHARSET and DB_COLLATE lines to wp-config.php without considering the consequences.

    Also please note, the WP-CACHE line is not part of the wp-config-sample.php delivered with WordPress.

    Resources:

    Editing wp-config.php
    Converting_Database_Character_Sets

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.