Yes, install domain_mapping.php in the mu-plugins folder.
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.
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.
@spherical Ron up there *is* one of the plugin authors. 😉
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.
Thanks Ron! Ok, I’ll move it to the /plugins folder.
@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.