Moderator
James Huff
(@macmanx)
Volunteer Moderator
Unless you set a custom table prefix, it should be all of the tables who’s name begins with wp_ .
I was thinking there are specific tables for the network setup – not all the table. ?
@macmanx if he deletes those, he deletes EVERYTHING.
multsite specifically adds a few extra tables when you install it. these are:
wp_blogs
wp_blog_versions
wp_registration_log
wp_signups
wp_site
wp_sitemeta
Any other tables with just wp_ are related to the main blog.
tables with a number in them like wp_2_posts are for the other sites/blogs.
Thanks andrea_r – I specifically emptied only wp_site and no longer am blocked from proceeding with the setup – but am getting this message
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.
which again points me away from using sub directories rather than sub domains – I think I should read up some more before continuing or at least start a new topic as I have drifted this one.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Sorry, I thought you meant that you wanted to delete everything. Oops.
– but am getting this message
…
which again points me away from using sub directories rather than sub domains –
It’s because the install is more than 30 days old, and this is a temporary workaround. You can force it to ignore this.
Actually, now that I read the initial post – there wasn’t a need to reinstall. If you didn’t add any new sites, you can change the kind sites that are made by changing the line in the config file.
define( ‘SUBDOMAIN_INSTALL’, true );
change it to
define( ‘SUBDOMAIN_INSTALL’, false );
For anyone else reading, if you have more sites in a subdomain format, this WILL NOT change exisiting links within them.
fresh install of 2.9.2, checked that all working, did the upgrade to 3.RC3 – again, all checked fine, then started the steps to enable multisite and got same message about old;-which it isn’t… made the above change to false and went through setup, created network, all seemed fine, created some sites (they show up in super admin) but they do not show up as a site, in super admin and selecting “backend” for a site, the dashboard doesn’t load either –
uhg ;(
When you did a fresh install, did you use an entirely new empty database?
Subfolders sites/blogs use mod_rewrite and the htaccess rules to display.
Hi Andrea
So just to confirm for us others reading this post if you were to delete all subdomain sites and then change this
define( ‘SUBDOMAIN_INSTALL’, false );
Everything would be work with subfolders?
Kind regards
Brad
It should. I haven’t tested it with 3.0 specifically, but it worked this way in MU, and there’s nothing much in there that changed.
And that change only affects WordPress. the server still has to be set up right.
When you did a fresh install, did you use an entirely new empty database?
Yes – used a “simple-scripts” install to setup a completely fresh install.
theory- could this be happening because this site was originally setup as a sub-domain and aliased to the url? I really don’t have the background to grasp all that’s involved here.
Don’t use Simple Scripts. Causes more issues that it helps. Seriously, it’s called a 5 minute install for a reason.
