WordPress.org

Forums

Uninstalling 3.1. Multisite (Enable Multisite plugin) (7 posts)

  1. still giving
    Member
    Posted 4 years ago #

    Having searched for how to uninstall multisite and applied the available suggestions, I keep coming up with a blank. The Multisite installer recognizes that there has been a previous install and will only offer a sub-domain install which then won't work.

    Is there a comprehensive and uptodate version or howto uninstall, as in which tables, columns and settings to remove from MySQL?

    This may not entirely be a WP issue. I was experimenting with the Enable Multisite plugin* to see if I could recommend it to non-techie others (I am perfectly capable of installing Multisite manually).

    * (I cannot recommend it at present. It does not seem to work in all installations but gives no information why or what when wrong.

    At the very least, it needs a working uninstaller, and more work done on it).

    Yes, I know ways around this as in just installing a new database and export/importing data etc but it would be a pain when all one should do is single click or use a single MySQL command.

    Thank you

    [moved from How-to to Multisite]

  2. Just tables. You leave the columns and settings alone, for the most part (or rather, there's no harm in leaving them ...).

    I'm pretty sure it's just these:
    wp_blogs
    wp_blog_versions
    wp_registration_log
    wp_signups
    wp_site
    wp_sitemeta

  3. and will only offer a sub-domain install which then won't work.

    this is becasue your install is more than 30 days old. the subfolder format stuffs a /blog/ in the permalinks, which would kill your exisiting links. that's why you get no choice.

    Subdomains not working is an issue with your host.

    uninstalling:

    http://wpmututorials.com/how-to/how-to-disable-multisite/

    (we need to write this up in the codex)

    I was experimenting with the Enable Multisite plugin* to see if I could recommend it to non-techie others
    * (I cannot recommend it at present.

    I'm in complete agreement with you.

  4. still giving
    Member
    Posted 3 years ago #

    Thank you for two confirmations that I am not being an idiot (re: codex and the plugin)! Folks ... don't try touch that plugin, it ain't finished yet by a long way.

    But my experience is that merely dropping those tables (which I tried) does not fix the issue. WP still recognises a previous install.

  5. WP still recognises a previous install.

    Exactly what do you mean?

    When you go to re-install a network it says a network is already detected, or it won't let you pick subfolders?

  6. still giving
    Member
    Posted 3 years ago #

    Example ... I have just dropped all the table as above, removed the changes to wp-config.php etc and am attempting a "fresh install". I get this:

    Error message.

    Sub-domain Install

    Because your install is not new, the sites in your WordPress network must use sub-domains. The main site in a sub-directory install will need to use a modified permalink structure, potentially breaking existing links.

    So I follow instructions setting it up as a sub-domain install and then, after logging in again, and /wp-admin/network.php offer me this:

    Create a Network of WordPress Sites

    Warning: An existing WordPress network was detected.

    ...

    define( 'SUBDOMAIN_INSTALL', false );

    A directory install.

    No Super Admin option.

    I just tried it again ... wp-config.php as it should be. .htaccess down exactly to just what WP-MS told me.

    So I tried a brand new database and it still stops me ... I am 90% sure it is the host and their DNS or "insecurity settings".

    Their tech tried to tell me, "I believe this is to do with php not being cgi on your server." Does not make sense to me ...

  7. So I tried a brand new database and it still stops me ... I am 90% sure it is the host and their DNS or "insecurity settings".

    If it's doing it on a brand new empty database, then yeah... something is up host side somewhere.

    Their tech tried to tell me, "I believe this is to do with php not being cgi on your server." Does not make sense to me ...

    No, the tech is incorrect. If php *was* being run as cgi on your server, it would be even more hosed. What host is this?

Topic Closed

This topic has been closed to new replies.

About this Topic