This is for multiple networks(many) sites.
You can just make him 4 sites under your wordpress multisite, with out this plugin.
You only need this if you want to give him 1 site, where he can make many sites under that site himself.
When you give him four sites, just make them “Unlisted” on your network.
Make him Admin of each of those 4 sites.
Unless you know this, and are wanting to give him 4 multisites, then don’t worry about my comment. 😉
– Just make sure your web server sends requests for all the domains you want under your install to the same filesystem path. Redirects will not work.
You can test it on the Networks admin page before creating the new network by filling in the domain and path you want to use, then clicking the link under “New Network Preview.” If you see the “No site defined on this host” error message, your web server is configured correctly.
– You can make him an admin on “network2” without giving him access to sites on “network1.” But you should only do this if you have a really good reason and trust him, because the user pool is shared and he will be able to install plugins and themes (which means arbitrary PHP code).
Just to be clear: if I get the error, I have it set up correctly? Pardon my denseness, but that seems counter-intuitive.
I may not make the client a super-admin, but at least the plugins I have on network2 don’t have to be on network1, correct?
Thanks for your reply.
Yep. WP throws that error because there’s no site (now called a “network”) on that domain… yet. But all you’re checking is that your web server is sending those requests to WP, so once you see the error, you know you’ve configured it correctly.
Obviously the error goes away once you actually create the network. 🙂
All plugins will be installed on all networks (there’s only one plugin folder), but can be activated per-network or per-site. And no, your client can’t use the Plugins admin page to activate plugins for network1 from network2.
