WPMU not adding new site :(

Did you deactivate it or did you have to completely remove the plugin?

I previously bypassed this issue by using a site I created, but stopped using a site we cancelled & replaced it with the new site I had to build. Now that site was finished, I went to map the full domain to that site in Domains->Domain Mapping and that wouldn’t add either.

Does WPMU use the 1st site as a template when it come to plugins, when creating a new site?

No it does not.

As I said above, same as when you install WP. Look in wp-admin/includes/schema.php & upgrades.php

those are what it uses to create a new site.

I noticed the only change (that can be related) is that in the “Must-Use” plugins page on the broken WPMU, there’s an “index.php” with “WordPress MU Domain Mapping” listed in the plugins. Whereas my other-yet-working WPMU install on another server only have “WordPress MU Domain Mapping”. Odd, considering the “mu-plugins” directory contents are identical.

I’m in the process of copying the exact core files that the working install has, to the broken install.

I’ve look thru the schema file. It sends out the email but somehow those tables aren’t getting created.

And for the life of me, I can’t figure out why “Network Setup” shows up in the Network Admin->Settings while my working install doesn’t have that.

After my copying, it changed nothing, but while adapting the working site’s wp-config.php to be identical to wp-config.php of the broken site (with obvious minor changes [MySQL, FTP, etc.]), I’m encountering some odd errors as well. Mainly database connection issues. Only the wp-config.php holds these settings, correct? I have to do some trial & error, but something is causing an db connection error despite the DB_* definitions are identical.

Alright I figured part of it out.

The install of WPMU’s site, in short, isn’t table-prefix_1_table-name, it’s just table_name. The SITE_ID_CURRENT_SITE & BLOG_ID_CURRENT_SITE is set to 1, while there is a blog in table_prefix_blogs with that ID, there the tables for that site are table-prefix_table-name.

(more to come as I figure out how to fix it)

It’s not WPMU anymore. If you say WPMU we think you’re using the old 2.9.2 stuff, so it does matter a bit! In fact, it matters right here because WPMU used to make a wp_1_* table, but WordPress MultiSite does not.

wp_<whatever> is correct for a 3.0-Multisite install. Now, for some reason, the DB self-repair doesn’t always get that, but that’s a separate issue.

Are your tables in the DB MyISAM or the other InnoDB?

Sorry, WPMU was just easier/quicker to type than Multisite.

All the tables are MyISAM.

I was able to put a band-aid on it by copying the non-numbered tables (having to do with content) over to a _1_ table.

Now, is there a way to reinstall without disrupting the existing sites? The primary site (that that subdomains are hosted on) isn’t used, so that can be messed with. But the subsequent subdomain sites that the domains are pointed to are the important ones.

Did you ever figure this out definitively? I’m having the same problem. I disabled all network plugins and tried again with no success. Should I disable everything?

Not really sure if I figured this out, but I disabled all I could and was then able to add sites.

I had this problem and it was solved turning off all plugins and then add new site. (this is for 3.2)

I’m having now a new problem: I made a plugin to create custom roles and capabilities and all custom roles are in all sites (these sites was created before the upgrade) except this new one.

In roles and capabilities documentation there are no support for WP 3.2 yet. Anyone had problems like these?

Guys, please make NEW topics ??