new changes in wp-config.php for WordPress MU 1.5.1

It has been closely two weeks since WordPress released its latest MU 1.5.1 version. I could not get a chance to upgrade mine till today. Normally I just upload all the newer files but wp-config.php to my server via FTPing. During this upgrading, I noticed that the last modified time for newer version of wp-config-sample.php has been changed. To find out what kind of changes inside, I opened the wp-config-sample.php file.


There are two new additions in the config file. 1) As WordPress 2.5, MU added Secret_Key variables in the config file (althoug I have no idea what they for); 2), Another change is a new contant which can allow you to set a URL to redirect if a blog does not exist. I like this one, since if somebody types a random directory name after my main domain, my MU will redirect him to a new registration page which I do not like at all.

Anyway, here is the detailed positions for these changes for your reference. 1) Secret_Key part:

Line 13 // Change SECRET_KEY to a unique phrase.  You won’t have to remember it later,
Line 14 // so make it long and complicated.  You can visit http://api.wordpress.org/secret-key/1.0/
Line 15 // to get a secret key generated for you, or just make something up.
Line 16 define(’SECRET_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase.
Line 17 define(’SECRET_SALT’, ‘put your unique phrase here’); // Change this to a unique phrase.

2), No-blog-existing redirection part:

Line 34 // Uncomment and set this to a URL to redirect if a blog does not exist. (Useful if signup is disabled)

Line 35 // Browser will redirect to constant( ‘NOBLOGREDICT’ ) . “?new=blogname” where blogname is the unknown blog
Line 36 // define( ‘NOBLOGREDIRECT’, ” );

If you want to implement the above configuration, you need to uncomment the line 36.

Additional note: In the process of upgrading WordPress MU or WordPress, please DO NOT disgard the current wp-config.php totally. Since maybe some your installed plug-ins had some useful codes in it. For example, mine has the following line generated by my wp_cache plug-in:

define(’WP_CACHE’, true); //Added by WP-Cache Manager

Tags: , , ,

Related posts

0 Responses to “new changes in wp-config.php for WordPress MU 1.5.1”


  1. No Comments

Leave a Reply