You should be able to activate on a per site basis so long as you have it active on the main site & any sites where you have a domain mapped.
The only option is to network activate it. If I don’t, then I cannot create new domains, let alone see them because the plugin options in Settings go away.
because the plugin options in Settings go away.
The plugin needs to be active on the main site in the network for the settings screen to be accessible in Network Admin.
Ah, ok, that sort of works. The sites I had created for testing are broken now. I can still access them but they look like their themes have gone away?
Must have been a browser cache or some other cache because this morning, the site/s look fine after making this change.
I was nervous about using a *.domainname because I have other main site sub-domains.
Adding the domains into the Apache conf as ServerAlias for the main site works fine for my needs.
Thanks much for the help.
“when I do that, all domain owners can then see the domain mapping functions in their site.”
Domain Mapping – /wp-admin/network/settings.php?page=dm_admin_page has a checkbox for “User domain mapping page”.
I have domain_mapping.php in wp-content/mu-plugins/ since it is a “must use” plugin, don’t want to ever deactivate it. (And sunrise.php must be in wp-content/ ). If you want some sites to be able to do their own mapping, but not others, put domain_mapping.php in the normal place (I haven’t done this, probably wp-content/plugins/wordpress-mu-domain-mapping/ )
Wildcard DNS (*.domainname) works fine with cPanel-created sub-domains; I have both. Seems that “actual sub-domains” take precedence over the “virtual sub-domains” of wildcard DNS. Easier than editing Apache conf, and works for people who don’t have access to editing that. Just don’t make WordPress sites with the same “virtual sub-domain name” as an actual sub-domain.
I think some get confused with the difference between sub DIRECTORY or sub-DOMAIN and multi-domain hosting.
In my case, I was having problems with a multi-domain setup, meaning, I want to host a bunch of different domains on this wp install. I have installs which are sub-directory or sub-domain and those simply take a wildcard DNS entry IF you don’t care that everything for that domain flows to the wp site OR if you have entries for those which should not in your DNS.
I can’t use a wildcard because wp doesn’t handle all of my sub-domains so I need certain things to go to other servers.
In terms of how I got this to work, which works perfectly now.
I just put the newdomain.mydomain.com into ServerAlias and DNS which gives wp what it needs.
Then, because dashboard is always broken, I went into the settings for each domain and changed the Home to the FQDN such as http://www.newdomain.com, leaving the rest as it is.
Now the user sees their site as they always have, they can log into the admin. From the Network wp, I can now click on dashboard of any domain and reach it instead of being sent out of the main site and into the domain.
And, this also fixed the URL problem in that domains had my domain as their pages and I needed them to have their own domain name, not mine.
All works as it should now it seems.
