As per title, we need to migrate a single site to an existing, live multisite (4 sub-sites already exist).

The multisite already has themes (theme X, theme Y, theme Z) and plugins (plugin A, plugin B, plugin C, plugin D, plugin E)

The single site has themes (theme X, theme Z, theme XXX) and plugins (plugin A, plugin B, plugin DDD, plugin FF)

What happens during migration? Are theme X, theme Z, plugin A, plugin B overwritten in multisite? Or will Prime Mover skip preexisting plugins/themes leaving them untouched?

Would we need to manually transfer each new theme/plugin (a delicate as well as tedious task), just export the database from the single site and then go through the whole process again every time we need to import a new single site as sub-site?

Does it work perfectly? What are the limitations?

I’m working on a blog based on a WordPress multi-site network (paths), where I intend to create a subsite to host the German language version of my blog.

I already added the German language site to my network and while it seems that the site is physically there, WordPress (i.e., the dashboard) is missing all relevant CSS. Simply, put, I can see the links of the subsite (in German), but they are missing the CSS.

When “visiting” the new subsite, it’s the same. I can see a page with some very basic CSS from my theme (Enfold), but it’s missing the proper CSS I defined in “Theme Options” of the Main site. I checked and the Enfold Theme is network-enabled, as is the Child Theme.

Please understand that I’m a rookie WordPress user. I have worked with multi-site installs before, but, if I remember correctly, the creation of subsites went off without a hitch and all CSS was derived automatically from the network-enabled theme and child theme.

Where am I going wrong here?

I would appreciate any tips and pointers. Thanks for your time and help with this.

KA

We first found that the form and its save feature were working fine for users who were on our campus. Then we got reports that the neither were working for users who were off-campus. They could fill out the whole form, but when they tried to save or submit, they would get an error. “An error occurred while processing the form. Please try again.” We were able to fix form submission by switching the submission method to Page Reload, rather than Ajax. However, there’s no similar option for Save and Continue.

Our situation is one of a multi-site server that has had some hardening to secure it. One example, that I suspect might be in play here, is that the ~/wp-admin subdirectory is restricted to on-campus users, (including those remote users using our VPN.) I’m hoping we can work with that.

Any way to remove Ajax from the save and continue process?

“Use main site configuration” seems like nothing else will be considered in the sub sites panel, but when we open the subsite cache panel for example:

https://imgops.com/1hr-tempcache/userUploadTempCache_ip187.75.78.64_utc_20240509-132928_new.png

We only see a warning on one item:
This setting is overridden by the main site setting, currently set to OFF

So just replace this setting? Do I have to configure everything else individually?

Source URL / [Ignore Case] [Ignore Slash]
Query Parameters: Ignore all parameters
Match: URL and server
Server: https://site-c.com
When matched: Redirect to URL with HTTP code 301 - Moved Permanently
Matched Target: https://www.site-b.com
Unmatched Target: https://www.site-b.com
Group: Redirections Position 1

Source URL / [Ignore Case] [Ignore Slash]
Query Parameters: Ignore all parameters
Match: URL and server
Server: https://www.site-c.com
When matched: Redirect to URL with HTTP code 301 - Moved Permanently
Matched Target: https://www.site-b.com
Unmatched Target: https://www.site-b.com
Group: Redirections Position 1

However, WP Network Multi-site is redirecting site-c.com to site-a.com and it seems that happens before redirection can take any action.

Here is what I have in my wp-config:

define( 'WP_ALLOW_MULTISITE', true);
define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', true );
define( 'DOMAIN_CURRENT_SITE', 'www.site-a.com' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );
define( 'ADMIN_COOKIE_PATH', '/' );
define( 'COOKIE_DOMAIN', '' );
define( 'COOKIEPATH', '' );
define( 'SITECOOKIEPATH', '' );
define( 'NOBLOGREDIRECT', 'https://www.site-a.com' );

If I exit; my wp-config file it will stay on site-c.com so I know that it is getting to my website and wordpress. It just seems that wordpress is redirecting first before redirection has a chance.

Does it have something to do with DOMAIN_CURRENT_SITE or NOBLOGREDIRECT?

Is there a way to have redirection handle the Server redirects for me so I don’t have to hard code them in PHP or my Web Server?

Thanks