Multisite upgrade breaks existing active component settings.

[DJPaul]

On a clean install of trunk and WP 3.2.1 (no multisite), install BP and activate as usual, accepting all the defaults presented in the setup wizard. This will have the default page slugs created, and all the components active.

Then enable your WP to run in multisite, by going through the normal WP_ALLOW_MULTISITE steps, etc. After the multisite is enabled, and you've logged back in re-enable BuddyPress network-wide, you'll get the Setup nag. Run through that process, again accepting the default page slug and component status.

What should happen is that everything remains active, and page mapping associations are intact. Instead, the components all deactivate themselves with the exception of Site Tracking which we've just turned on again. Page mapping also appear to be broken. See screenshot.

[DJPaul]

Note, I had switched to BP-Default as part of the non-multisite install process. After the multisite switch and upgrade process, the active theme is still BP-Default and still works when I visit the front of the web site, despite the text in the nag box claiming otherwise.

[DJPaul]

I've attached a patch that seems to fix the issues of the components and page mappings being lost after multisite is activated. It needs looking at by someone more familiar with the installer/upgrade wizard please

[boonebgorges]

Tested. Looks good, DJPaul.

[djpaul]

(In [4978]) Fix multisite upgrading loosing existing component activation settings and page mapping. Fixes #3473