WordPress 中文文档

From WordPress Chinese

As part of the WordPress installation, you must modify the wp-config.php file to define the WordPress configuration settings required to access your MySQL database.

This file, wp-config.php, does not exist in a downloaded copy of WordPress; you need to create it. The wp-config-sample.php file is provided as an example to work from.

To change the wp-config.php file for your installation, you will need this information:

• Database Name
• Database Username
• Database Password
• Database Host

If your hosting provider installed WordPress for you, get the information from them. If you manage your own web server or hosting account, you will have this information as a result of creating the database and user (see Installing WordPress, Create the Database and User).

Creating the file

Open the file wp-config-sample.php in a text editor.

Important: never use a word processor like Microsoft Word for editing WordPress files!

Database name

Find the line that says:

define('DB_NAME', 'putyourdbnamehere'); // The name of the database

(NOTE: Everything on these lines you see after the // are comments for information purposes only.)

Where it says 'putyourdbnamehere', delete putyourdbnamehere and enter the name of your database. Make sure that you don't accidentally delete the single quotation marks!

The line should look like this:

define('DB_NAME', 'myDatabasename'); // The name of the database

Database user name

define('DB_USER', 'usernamehere'); // Your MySQL username

Delete usernamehere and enter in your own username:

define('DB_USER', 'myDatabaseUser'); // Your MySQL username

Database password

On to the next one:

define('DB_PASSWORD', 'yourpasswordhere'); // ...and password

Delete yourpasswordhere and enter in your MySQL password:

define('DB_PASSWORD', 'MyOwnPassword'); // ...and password

This is only an example password, of course! :)

Database host

The next line under the password line defines the host for your database. There is a 99% chance you will NOT have to change it unless your web host tells you otherwise. In other words, you can likely leave it as the default value of 'localhost'.

If your database host is different than 'localhost', move down to the next line:

define('DB_HOST', 'localhost');     // 99% chance you won't need to change this value

Delete localhost and enter in your database host as directed by your web host:

define('DB_HOST', 'mysql34.myhostserver');     // 99% chance you won't need to change this value

Of course, the mysql34.myhostserver will be different for you.

Possible DB_HOST values

Some possible DB_HOST vales for hosting companies:

• BlueHost - 'localhost'
• AN Hosting - 'localhost'
• HostICan - 'localhost'
• DreamHost - user creates the database name
• LaughingSquid - 'localhost'
• Yahoo - 'mysql'
• GoDaddy - something similar to 'h41mysql52.secureserver.net'
• 1and1 - something similar to 'db12345678'
• one.com - 'localhost'
• Hosts with cPanel - 'localhost'
• Host with Plesk - 'localhost'

Mysql Alternate Port

Also if your database host uses an alternate port number you'll need to change to reflect the alternate port:

define('DB_HOST', 'mysql34.myhostserver:3307');     // 99% chance you won't need to change this value

You'll need to change 3307 to reflect what your host provides you as the alternate port number.

Database character set

As of WordPress Version 2.2, DB_CHARSET was made available to allow designation of the database character set (e.g. tis620 for TIS620 Thai) to be used when defining the MySQL database tables. The default value of utf8 (Unicode UTF-8) should NOT BE CHANGED without careful understanding of the outcome. Please note that UTF-8 supports many European languages so leave DB_CHARSET at utf8 and use the appropriate DB COLLATE value for your language.

• Warning for those performing new installations: For most Western European languages, including English, there usually 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 That MySQL Supports for the valid values for DB_CHARSET.
• 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!"

This example shows utf8 which is considered the WordPress default value:

define('DB_CHARSET', 'utf8');

Database collation

As of WordPress Version 2.2, DB_COLLATE was made available to allow designation of the database collation (i.e. the sort order of the character set). In most cases, this value should be left blank (null) so the database collation will be automatically assigned by MySQL based on the database character set (i.e. DB_CHARSET). Set DB_COLLATE to one of the UTF-8 values defined in Unicode character sets (utf8 section) for most Western European languages.

• Warning for those performing new installations: There usually should be no reason to change the default value of DB_COLLATE. Leaving the value blank (null) will insure the collation is automatically assigned by MySQL when the database tables are created.
• Warning for those performing upgrades: If DB_COLLATE and DB_CHARSET 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_COLLATE and DB_CHARSET to the wp-config.php file, for an existing blog, can cause problems — as Ryan Boren says, "your queries will go boom!"

This example is of the WordPress default DB_COLLATE value:

define('DB_COLLATE', ''); 

• Example if UTF-8 Unicode Turkish collation is needed (DB_CHARSET should be utf8):

define('DB_COLLATE', 'utf8_turkish_ci'); 

$table_prefix

The $table_prefix is the value placed in the front of your database tables. Change the value if you want to use something different than wp_ for your database prefix. Typically this is changed if you are installing multiple WordPress blogs in the same database.

Advanced Options

WordPress address (URL)

Another new wp-config.php option, added as of WordPress Version 2.2, is WP_SITEURL. This allows the WordPress address (URL) to be defined. The valued defined is the address where your WordPress core files reside. It should include the http:// part too. Do not put a backslash "/" at the end. Setting this value in wp-config.php causes the wp_options table option_value of siteurl to be set and disables the WordPress address (URL) field in the Administration > Options > General panel.

If you have installed WordPress into a directory called "wordpress" in a domain name called "sample.com", define WP_SITEURL as this example does:

define('WP_SITEURL', 'http://www.sample.com/wordpress'); 

Blog address (URL)

WP_HOME is another wp-config.php option added in WordPress Version 2.2. This allows the Blog address (URL) to be defined. This is the address you want people to type in their browser to reach your WordPress blog. It should include the http:// part. Also, do not put a backslash "/" at the end. Setting this value in wp-config.php causes the wp_options table option_value of home to be set, and disables the Blog address (URL) field in the Administration > Options > General panel.

define('WP_HOME', 'http://www.sample.com/wordpress'); 

If you are using the technique described in Giving WordPress Its Own Directory then follow the example below. Remember, you will also be placing an index.php in your web-root directory if you use a setting like this.

define('WP_HOME', 'http://www.sample.com'); 

Debug

The WP_DEBUG option, added in WordPress Version 2.3.1, if set to true, means that errors will be reported to the user. If set to false, no errors will be reported. If this setting is absent from wp-config.php, then the value is assumed to be false (no error reporting). Note that the true and false values are not set in apostrophes (').

Error report is turned ON (errors reported to user):

define('WP_DEBUG', true);

Error reporting is turned OFF (no errors reported):

define('WP_DEBUG', false);

Secret key (for salting)

As of WordPress 2.5 (not yet released) there is a new optional entry, called SECRET_KEY, that causes better encryption of user passwords in the database. The secret key is a unique phrase.

define('SECRET_KEY', 'put your unique phrase here'); // Change this to a unique phrase. 

Increasing memory allocated to PHP

Beginning with WordPress 2.5 (not yet released), the new WP_MEMORY_LIMIT option allows you to specify the maximum amount of memory that can be consumed by PHP. This setting may be necessary in the event you receive a message such as "Allowed memory size of xxxxxx bytes exhausted".

This setting increases PHP Memory only for WordPress, not other applications. By default, WordPress will attempt to increase memory allocated to PHP to 32MB (code is at beginning of wp-settings.php), so the setting in wp-config.php should reflect something higher than 32MB.

Please note, this setting may not work if your host does not allow for increasing the PHP memory limit--in that event, contact your host to increase the PHP memory limit. Also, note that many hosts set the PHP limit at 8MB.

Increase PHP Memory to 64MB

define('WP_MEMORY_LIMIT', '64MB');

Increase PHP Memory to 96MB

define('WP_MEMORY_LIMIT', '96MB');

Cache

The WP_CACHE setting, if true, includes the wp-content/advanced-cache.php script, when executing wp-settings.php.

define('WP_CACHE', true); 

Double Check Before Saving

Be sure to check for leading and/or trailing spaces around any of the above values you entered, and DON'T delete the single quotes!

Before you save the file, be sure to double-check that you have not accidentally deleted any of the single quotes around the parameter values. Be sure there is nothing after the closing PHP tag in the file. The last thing in the file should be ?> and nothing else. No spaces.

To save the file, choose File > Save As > wp-config.php and save the file in the root of your WordPress install. Upload the file to your web server and you're ready to install WordPress!

wp-config.php with Multiple Blogs

Multiple WordPress blogs require special handling of their configuration files. Check Installing Multiple Blogs for more information.