Upgrading from WPMu to WP 3.0: Keep your config!

I just updated to the latest version of WordPress 3.0 (release candidate 1) and one of the things I realized while upgrading my own sites is that you should really keep your WPMu wp-config.php file. I figured that I would need to use the updated config file with WP 3.0, but that’s not necessarily the case. You see, the wp-config.php file is still geared towards a single WP install, which makes sense, but it also leaves a ton of the essential defines for a mutli-site system completely out.

So, here is a quick look at my wp-config file, with bold annotations of what you should keep if you are doing the multi-site option:
// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'database_name_here');
/** MySQL database username */
define('DB_USER', 'username_here');
/** MySQL database password */
define('DB_PASSWORD', 'password_here');
/** MySQL hostname */
define('DB_HOST', 'localhost');
/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');
/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');
//Note: the following elements are specific to a WPMu/Multi-Site setup, and there is no sign of them in the config file for 3.0, so be sure to copy them over. But comment out
define('DOMAIN_CURRENT_SITE', 'yourmaindomain.com' ); -if you have issues on a multi-site setup because that one was giving me redirect problems on my setup.
/** The Database Collate type. Don't change this if in doubt. */
define('VHOST', 'yes');
$base = '/';
//define('DOMAIN_CURRENT_SITE', 'yourmaindomain.com' );
define('PATH_CURRENT_SITE', '/' );
define('BLOGID_CURRENT_SITE', '1' );
//End Note.
/**#@+
* Authentication Unique Keys and Salts.
define('AUTH_KEY', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');
* Change these to different unique phrases!
* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1...;WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each a unique
* prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';
/**
* WordPress Localized Language, defaults to English.
*
* 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', '');
/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
define('WP_DEBUG', false);
//Note: sunrise.php is specifically for mapping domains on blogs, and you will need to include this in your wp-config file for multi-site if you want to map domains.
// uncomment this to enable wp-content/sunrise.php support
define( 'SUNRISE', 'on' );
//End Note.
/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )

define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);

That’s it, really not too bad, but enough to screw an idiot like me up, so I figured I’d share it out.

This entry was posted in , wordpress multi-user, wp30, wpmu, wpmu development, wpmued. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *