We've been using the domain mapping plugin for a few years and have always followed the instructions which indicate placing sunrise.php in wp-content and domain-mapping.php into mu-plugins. The newer versions of the plugin also include a classes and images folders and the like, which aren't used or uploaded if you follow the instructions as it looks like the instructions are a bit out of date .... What are proper installation instructions?
We've been using the domain mapping plugin for a few years and have always followed the instructions which indicate placing sunrise.php in wp-content and domain-mapping.php into mu-plugins. The newer versions of the plugin also include a classes and images folders and the like, which aren't used or uploaded if you follow the instructions as it looks like the instructions are a bit out of date .... What are proper installation instructions?
At the moment the plugin can either be installed as per the current instructions (copy domain-mapping.php to the mu-plugins directory and sunrise.php to wp-content), or it can be installed as a standard network plugin (copy the domain-mapping directory to the plugins directory and network activate).
We are moving towards the latter being the standard method, and from the next release that will be the recommended method. This is primarily because it allows us easier control over the location of the translation files (.po and .mo) which has always been troublesome with plugins uploaded to the mu-plugins directory.
If you need the plugin to be translatable now, then the latter is the method to go, as the original instructions mean that the translation files are not uploaded and therefore not used.
I'll make sure that we update the installation instructions so that both methods are shown.
Barry, thank you for the fast response.... updated to network activate method and sunset.php is still required in wp-content ... if anyone is wondering.
Just a heads up, the 301 redirect is actually a 302 temporary redirect unless the "true" are added per below on lines 791 to 793. I've brought this up in a few threads and you actually wrote the fix a couple of years ago but it still hasn't been implemented in the plugin ... just a heads up. :)
Responses (6)
Sales & Support Pro — 12th January 2012 (4 months ago) #
Hiya!
Let me just seek clarification from the developer on that one...
Thanks,
Phil
Lifetime Member — 12th January 2012 (4 months ago) #
Hiya,
Mark started a new topic for that.
Check it -> http://premium.wpmudev.org/forums/topic/upgrade-from-305-306-multi-db#post-170029
I hope that's help.
Member — 12th January 2012 (4 months ago) #
Thanks. I'm not confident that thread is accurate, so we'll sit tight until a dev chimes in.
Developer — 12th January 2012 (4 months ago) #
At the moment the plugin can either be installed as per the current instructions (copy domain-mapping.php to the mu-plugins directory and sunrise.php to wp-content), or it can be installed as a standard network plugin (copy the domain-mapping directory to the plugins directory and network activate).
We are moving towards the latter being the standard method, and from the next release that will be the recommended method. This is primarily because it allows us easier control over the location of the translation files (.po and .mo) which has always been troublesome with plugins uploaded to the mu-plugins directory.
If you need the plugin to be translatable now, then the latter is the method to go, as the original instructions mean that the translation files are not uploaded and therefore not used.
I'll make sure that we update the installation instructions so that both methods are shown.
Member — 12th January 2012 (4 months ago) #
Barry, thank you for the fast response.... updated to network activate method and sunset.php is still required in wp-content ... if anyone is wondering.
Just a heads up, the 301 redirect is actually a 302 temporary redirect unless the "true" are added per below on lines 791 to 793. I've brought this up in a few threads and you actually wrote the fix a couple of years ago but it still hasn't been implemented in the plugin ... just a heads up. :)
' Header( "Location: " . $url . $request, true, 301);
} else {
Header( "Location: " . $url . $_SERVER[ 'REQUEST_URI' ], true, 301 );
'
Member — 21st January 2012 (4 months ago) #
Any ypdates on this? As I plan on installing this soon and wondered if something had changed.
Become a member