• Anyone out there have detailed instructions reverting your wordpress multi site install to standard wordpress?

    I’ve found conflicting info on the web and its somewhat vague…

    Option 1:

    All you need to delete this code;

    define( ‘MULTISITE’, true );
    define( ‘SUBDOMAIN_INSTALL’, false );
    $base = ‘/’;
    define( ‘DOMAIN_CURRENT_SITE’, ‘localhost’ );
    define( ‘PATH_CURRENT_SITE’, ‘/’ );
    define( ‘SITE_ID_CURRENT_SITE’, 1 );
    define( ‘BLOG_ID_CURRENT_SITE’, 1 );

    After removing above lines now change the disable the multisite feature by replacing true word with false;

    define(‘WP_ALLOW_MULTISITE’, true);

    But moving onward to disable unwanted feature, do remove extra sites that are hosted on same wordpress installation and follow above procedure.

    Before editing your config file make a backup of it and enjoy WordPress 3.0 with disable multisite feature.

    Option 2:
    * Remove all the lines added to wp-config.php
    * Revert back to older .htaccess file or delete it and regenrate it by going to Settings > Permalinks
    * Remove the two fields added to the users table that are multisite-only (deleted and spam columns).
    * Remove the following tables in database
    (prefixed by your DB prefix which is generally wp_):
    o wp_blogs
    o wp_blog_versions
    o wp_registration_log
    o wp_site
    o wp_sitemeta
    o wp_signups
    o wp_sitecategories (if you have global terms enabled)

Viewing 15 replies - 1 through 15 (of 16 total)
  • Those two are almost identical, but the first one has this incorrect info:

    After removing above lines now change the disable the multisite feature by replacing true word with false;

    define(‘WP_ALLOW_MULTISITE’, true);

    Just remove the line.

    If you really want me to pick one, #2 was thorough.

    (man I really need to write this up).

    Thread Starter dodonest

    (@kenazar)

    That would really help. There’s so much on the web that’s mixed regarding this topic. Removal of one line could really screw up the install?

    Could you put me on a list to notify me once its written up?

    Best,
    Ken

    Thread Starter dodonest

    (@kenazar)

    I noticed my config file does not have this…

    define(‘WP_ALLOW_MULTISITE’, true);

    This is my config file…

    <?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 https://codex.www.ads-software.com/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(‘WP_CACHE’, true); //Added by WP-Cache Manager
    define(‘DB_NAME’, ‘xxxx’);

    /** MySQL database username */
    define(‘DB_USER’, ‘xxxx’);

    /** MySQL database password */
    define(‘DB_PASSWORD’, ‘xxxx’);

    /** 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’, ‘yes’);
    $base = ‘/’;
    define(‘DOMAIN_CURRENT_SITE’, ‘xxxx’ );
    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 https://trac.mu.www.ads-software.com/ticket/1169 */
    //define( “EDIT_ANY_USER”, true );
    /* Uncomment to enable post by email options. See https://trac.mu.www.ads-software.com/ticket/1084 */
    //define( “POST_BY_EMAIL”, true );

    /**#@+
    * Authentication Unique Keys.
    *
    * Change these to different unique phrases!
    * You can generate these using the {@link https://api.www.ads-software.com/secret-key/1.1/wpmu/salt www.ads-software.com 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
    */
    define(‘AUTH_KEY’, ‘xxxx’);
    define(‘SECURE_AUTH_KEY’, ‘xxxx’);
    define(‘LOGGED_IN_KEY’, ‘xxxx’);
    define(‘NONCE_KEY’, ‘xxxx’);
    define(‘AUTH_SALT’, ‘xxxx’);
    define(‘LOGGED_IN_SALT’, ‘xxxx’);
    define(‘SECURE_AUTH_SALT’, ‘xxxx’);
    /**#@-*/

    /**
    * 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 https://examples.com/ for the following: define( ‘NOBLOGREDIRECT’, ‘https://example.com/&#8217; );
    // 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 );

    define( ‘NONCE_SALT’, ‘xxxxxx’ );

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

    You have a wordpressmu install, or one that was upgraded from mu to 3.0.

    Where are you hosted?

    Thread Starter dodonest

    (@kenazar)

    I had everything at hostgator now at hostnine…

    I’m concerned with all the work on the existing theme that I’ve done Can I piece together from a cpanel backup the theme layout settings etc… and db

    Sure, just grab all the wp_1_options tables. That;s where the theme should have stored any settings.

    It’s a different process to switch from a wpmu install to a single wordpress install. that’s why what you’re reading was confusing – it didn’t even apply.

    You have to set up a fresh singe WP install and import the content into it, plus the options table I named above.

    Thread Starter dodonest

    (@kenazar)

    Should I export all wp_1_option tables through phpadmin? I would then import them to phpadmin? Do I need to have them read wp_option to work?

    Can I export all the pages and post through the standard tools–>export?

    Should that cover everything to get up and running with the existing layout, theme and images?

    Thanks,
    Ken

    Yes. You’ll have to copy over the entire wp-content folder too.

    and you’ll have to do some fun moving aroudn with the uploads, but we’ll deal with that when you get there.

    Thread Starter dodonest

    (@kenazar)

    Is this spelled out anywhere so there not any downtime? Will you be around in the next hour to help me out via chat?

    No, and no. ??

    We’re all volunteers here. I just pop in and help where I can.

    Thread Starter dodonest

    (@kenazar)

    Okay I have the new install with my old wp-content directory uploaded…

    Do I import the wp_1_option tables now via phpmyadmin?

    yes, you’ll need to rename it to wp_options tho (or whatever matches your new install).

    Thread Starter dodonest

    (@kenazar)

    Is there a way to change them all to read wp_options at once?

    Thread Starter dodonest

    (@kenazar)

    I think I got everything up and running… I just need to know where to put the previous image from blog.dir 1

    Whatever the new wordpress install has set for the uploads folder. ?? Usually wp-content/uploads/files/

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Detailed Documentation – Downgrade Multisite to regular wordpress’ is closed to new replies.