Support » Plugins » [Plugin: WordPress MU Domain Mapping] Upgrade & mu-plugins Directory

  • Resolved Ryan Bickett

    (@rbickett)


    I’ve successfully upgraded the WordPress MU Domain Mapping plugin to version 0.5.4 in my multisite WordPress 3.1 site network, but I have a quick question. Should I be moving the “domain_mapping.php” file from the “mu-plugins” directory to the standard “plugins” directory or should I leave it where it is? I read the following line in the readme.txt file and was a little confused. Thanks!

    Illustrated installation instructions can be found [here](http://ottopress.com/2010/wordpress-3-0-multisite-domain-mapping-tutorial/) but you can ignore the instructions to place domain_mapping.php in mu-plugins.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Yes, install domain_mapping.php in the mu-plugins folder.

    Thread Starter Ryan Bickett

    (@rbickett)

    Ok, great. That’s how I have it, but just got a little confused. Thanks!

    ?

    The instructions in the 0.5.4 version clearly state to install the plugin in /plugins and Network Activate it now and the statement in the readme (cited above) say that as well. I suppose that it may make no difference but, then, the docs should say that. I moved mine to where the instructions said. It works perfectly and restored the missing domain callouts in the Sites Admin page that disappeared after a 3.1 upgrade.

    I just found out about the docs change.

    Thread Starter Ryan Bickett

    (@rbickett)

    So, should we be following the docs and readme.txt file suggestion and use the /plugins folder instead of /mu-plugins? I just want to make sure I am following the best approach.

    That is what the plugin authors state, yes. That’s why they wrote the instructions. Although it also probably works from /mu-plugins, as you’ve found out, the move to /plugins is the new approach and it will be this way going forward for the foreseeable future. Nothing to be afraid of [standard disclaimers apply] 🙂 but I have it in the new location and it works better with 3.1 from there. And, it will better be able to notify blog admins of a new version that has been pushed to the servers for update.

    Thread Starter Ryan Bickett

    (@rbickett)

    @spherical – Thanks!

    @spherical Ron up there *is* one of the plugin authors. 😉

    Thread Starter Ryan Bickett

    (@rbickett)

    So, to be sure I am clear. Since Ron states above that this plugin should still be placed in the /mu-plugins folder that is where we should be placing it, correct?

    @rbickett – When I posted above I wasn’t aware that Donncha had changed the installation instructions.

    Thread Starter Ryan Bickett

    (@rbickett)

    Thanks Ron! Ok, I’ll move it to the /plugins folder.

    spherical

    (@spherical)

    @andrea_r

    @spherical Ron up there *is* one of the plugin authors. 😉

    I know.

    That’s one of the reasons it didn’t make any sense but I figured that what’s in the Docs is what’s in the Docs and that worked for me, so shared to the OP.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Upgrade & mu-plugins Directory’ is closed to new replies.