The Network creation panel is not for WordPress MU networks.

Thanks for the response.

Then how can I get rid of the nag that says, “Thank you for Updating! Please visit the Update Network page to update all your sites.”? Are you saying that, if I did create a second site, that I then would be able to click the link to Network Admin and would see something other than, “The Network creation panel is not for WordPress MU networks.”? TIA!

Andrea_r, thanks for the reply. I wonder if there is something wrong with my WPMU, for I don’t see a way to add a second site. While logged in as admin I see Dashboard/My Sites. On the My Sites page, it lists the primary site and offers links to visit or dashboard. I don’t see an add site option. Can you please clue me in?

This is why I think something is wrong with my site. When I go to http://iyta.org/wp-admin/network, I get that message, “The Network creation panel is not for WordPress MU networks.” I have no idea how to fix it. Suggestions?

I’m lost. Ipstenu, when I upgraded from 3.0, I just did the automatic upgrade.

This is the code in the wp-config.php (with the DB password replaced with {snip}):

<?php
/**
 * The base configurations of the WordPress.
 *
 **************************************************************************
 * Do not try to create this file manually. Read the README.txt and run the
 * web installer.
 **************************************************************************
 *
 * This file has the following configurations: MySQL settings, Table Prefix,
 * Secret Keys, WordPress Language, and ABSPATH. You can find more information by
 * visiting {@link http://codex.wordpress.org/Editing_wp-config.php Editing
 * wp-config.php} Codex page. You can get the MySQL settings from your web host.
 *
 * This file is used by the wp-config.php creation script during the
 * installation.
 *
 * @package WordPress
 */

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'SNIP');

/** MySQL database username */
define('DB_USER', 'SNIP');

/** MySQL database password */
define('DB_PASSWORD', '{snip}');

/** 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', '');
define('VHOST', 'no');
#$base = '/~iytaorg/';
$base = '/';
#define('DOMAIN_CURRENT_SITE', '66.147.240.198' );
define('DOMAIN_CURRENT_SITE', 'iyta.org' );
#define('PATH_CURRENT_SITE', '/~iytaorg/' );
define('PATH_CURRENT_SITE', '/' );
define('SITE_ID_CURRENT_SITE', 1);
define('BLOGID_CURRENT_SITE', '1' );

/* Uncomment to allow blog admins to edit their users. See http://trac.mu.wordpress.org/ticket/1169 */
//define( "EDIT_ANY_USER", true );
/* Uncomment to enable post by email options. See http://trac.mu.wordpress.org/ticket/1084 */
//define( "POST_BY_EMAIL", true );

/**#@+
 * Authentication Unique Keys.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link http://api.wordpress.org/secret-key/1.1/wpmu/salt 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
 */
[CUT]
{snip}

/**
 * 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', '');

// double check $base
if( $base == 'BASE' )
	die( 'Problem in wp-config.php - $base is set to BASE when it should be the path like "/" or "/blogs/"! Please fix it!' );

// uncomment this to enable WP_CONTENT_DIR/sunrise.php support
//define( 'SUNRISE', 'on' );

// uncomment to move wp-content/blogs.dir to another relative path
// remember to change WP_CONTENT too.
// define( "UPLOADBLOGSDIR", "fileserver" );

// If VHOST is 'yes' uncomment and set this to a URL to redirect if a blog does not exist or is a 404 on the main blog. (Useful if signup is disabled)
// For example, the browser will redirect to http://examples.com/ for the following: define( 'NOBLOGREDIRECT', 'http://example.com/' );
// Set this value to %siteurl% to redirect to the root of the site
// define( 'NOBLOGREDIRECT', '' );
// On a directory based install you must use the theme 404 handler.

// Location of mu-plugins
// define( 'WPMU_PLUGIN_DIR', '' );
// define( 'WPMU_PLUGIN_URL', '' );
// define( 'MUPLUGINDIR', 'wp-content/mu-plugins' );

define( "WP_USE_MULTIPLE_DB", false );

/* That's all, stop editing! Happy blogging. */
define( 'NONCE_SALT', {snip}

/** 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');

Andrea_p, with and without the slash and going to the URL you suggested, http://iyta.org/wp-admin/network.php, takes me to http://iyta.org/wp-admin/network/setup.php and that displays the message, “The Network creation panel is not for WordPress MU networks.”

Thanks everyone for your help!

Well, after an hour on the phone with hostmonster.com, the host did not help. They said I would need to post a support ticket. I’m going to do that, but was told it would be a couple of days until I should expect a reply. Seems like I am stuck.

I suspect that this is a legacy of having originally installed WPMU before WP3.0 came out. I wonder if I should somehow save my site and the custom plugins that were added to it and do a fresh install of WP and then set up the site again. That seems like a drastic measure.