Thanks, someone else had already reported that so it’s on the list to fix.
I think this is what I just fixed. Spent like a half hour sprinkling echos throughout the plugin and WordPress. Making domain_mapping_plugins_uri check that the replacement it wanted to perform was actually possible did the trick for me:
function domain_mapping_plugins_uri( $full_url, $path=NULL, $plugin=NULL ) {
if (stripos( $full_url, PLUGINDIR ) == FALSE)
return get_option( 'siteurl' ) . $full_url;
return get_option( 'siteurl' ) . substr( $full_url, stripos( $full_url, PLUGINDIR ) - 1 );
}
We had this same issue and resolved it by moving the plugin to mu-plugins and calling the domain mapping file properly.
<?php
require(‘wordpress-mu-domain-mapping/domain_mapping.php’);
?>
in /mu-plugins/wordpress-mu-domain-mapping.php
Magically delicious.
Does anyone have an opinion on the best/easiest way of addressing the plugins directory issue?
In my WPMU subdirectory install, when I–as Super Admin–upload a new plugin, the zip file ends up in /wp-content/uploads/2013/06 (instead of /wp-content/plugins/).
@pablo – you’re not supposed to upload it you are supposed to install it through the network -> plugins screen.
Thanks for the fix Egypt. Worked for us.
Since this plugin is no longer in the mu-plugins folder, are some plugins running before the ‘plugins-url’ filter is added?
Does the MU Plugin now work with different wp-content dir ?
