Support » Plugin: WordPress MU Domain Mapping » [Plugin: WordPress MU Domain Mapping] Appears no longer to be necessary

  • Sixes


    This plugin appears no longer to be necessary. I simply renamed the sites in Network Admin and the domains mapped perfectly.

    Indeed, it cured the looping problem that was occurring and also meant that the wp-admin page related to the actual domain name.

    I’m running under nginx. I haven’t tested this under Apache.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hirs


    How do you exactly made it work? I have changed the domain name in the blog options, apparently it works, but I can’t login to wordpress, I just get back to the login screen, no error reported



    Hey, Sixes, thanks for this great info!

    Can you please give us more details on how this is done? I.e., how do you “rename” a site in Network Admin?

    Here is the path I know (WP 3.3.1):

    My Sites->Network Admin->Sites->Edit (for the specific site)->Info->Domain

    Is the Domain field the one that you rename, as Hirs suggested? Do you have a solution for the login problem?

    Thanks in advance!



    Hi Sixs

    Would be great to get a bit more information on setup


    I’m able to get any domain working without the plugin as well.
    – I’ve got a subdomain multisite installation.
    – I add a new site, giving it a dummy subdomain.
    – In the notice, I click on “Edit Site”.
    – I change the domain to whatever.
    – If I visit the site immediately, I get a fatal error. But it’s in a plugin (google analytics).
    – If I go to /wp-login.php, and then back to the homepage (without logging in), the error goes away.
    – I can log in fine.

    The domain mapping plugin does provide features, like allowing people to create their own sites. But I’m just using multisite for a multilanguage site, so I’m creating the handful of sites upfront as the super admin.

    I always found it strange that domain mapping was not core to multisite. Is it the case that the functionality is being moved in?

    OK. After a lot more playing, it seems that this plugin *is* necessary to get things set up but is still causing a looping issue for me.

    My “fix” at the moment is to install the plugin, add the new domain-mapped name and then to remove the plugin again. That way the looping issue goes away and the mapped domain still appears to work.

    Sorry for anyone I confused with my first post (especially me) 🙂

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Appears no longer to be necessary’ is closed to new replies.