Beating my head on this. I've been through forums, andrea_r's posts/slideshows and the docs several times.
Seems most people are using subdomain installs on this though, according to the plugin, it 'recently' began supporting subdirectory installs.
If you can help here or point me in the right direction, I'd be really grateful.
My understanding is that users can modify their A/Cname record to point to our site "mybasedomain.com", then under Tools | Domain Mapping, map "myblogdomain.com" to "mybasedomain.com/myblog" and booyah - great joy.
Except I'm not feeling the joy. In doing so, "myblogdomain.com" in the browser is in fact landing at "mybasedomain.com".
Excellent. It 'seems' to me that the DNS for "myblogdomain.com" is doing it's part and getting the user to our server.
However, why isn't it finishing the last step and A) at a minimum, redirecting them to "mybasedomain.com/myblog" or B) ideally, showing "myblogdomain.com" in the URL while displaying "mybasedomain.com/myblog" content?
Here's what I have at the bottom of wp-config.php:
define('WP_DEBUG', false); define ('WP_ALLOW_MULTISITE', true ) ; define( 'MULTISITE', true ); define( 'SUBDOMAIN_INSTALL', false ); $base = '/'; define( 'DOMAIN_CURRENT_SITE', 'lifemapp.com' ); define( 'PATH_CURRENT_SITE', '/' ); define( 'SITE_ID_CURRENT_SITE', 1 ); define( 'BLOG_ID_CURRENT_SITE', 1 ); /* That's all, stop editing! Happy blogging. */ /** Absolute path to the WordPress directory. */ if ( !defined('ABSPATH') ) define('ABSPATH', dirname(__FILE__) . '/'); /** WordPress MU Domain Mapping plugin */ define( 'SUNRISE', 'on' ); /** Sets up WordPress vars and included files. */ require_once(ABSPATH . 'wp-settings.php');
Again, really appreciate ANY direction/pointers to solve this.