[Plugin: WordPress MU Domain Mapping] domain mapping to subdirectory

  • 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.

Viewing 8 replies - 16 through 23 (of 23 total)

  • is the domain parking (server side) a necessity only when having a shared IP environment or shared hosting with multiple wordpress installs?

    Domain parking is a cpanel term. If you’re on another host, they may call it something different. In Apache, you’re making a serveralias.
    If you’re on a dedicated box, then the best way is to have a wildcard named host.

    So the parking bit is really “it depends on your web host”.

    The big key to this – which you already figured out – is configuring the server itself to send domain names to the proper location. Once the hits the server, it sends it to the wordpress install and then the plugin kicks in.

    Thread Starter ddarby14

    (@ddarby14)

    I think the parking (or serveralias or whatever the flavor) is the catch for people, at least it was for me, maybe Mark. Not in the terminology or employment, but in terms of added effort/management.

    We’re not using serveraliases at all, so therefore the plugin is working as I expected – whereas client can come and go with using our services/pointing their own domains, we never have to think about it.

    We’re also not using wildcard host (I believe that is only for the subdomain version and we’re only using subdirectory).

    I really would not want a setup in which, say I get 1000 users who add 1000 domains and requires our team to add 1000 serveraliases – oy, that is a nightmare. Our goal is always to create a self-managed system so that we (the host/supplier) are never a hurdle/manager for clients. ??

    With the way we have it setup (still guessing it’s because only 1 install per server or IP), our team does nothing at all in the process.

    It’s all up to client to a) add CNAME (or A) record and b) add matching entry to Domain Manager.

    Thread Starter ddarby14

    (@ddarby14)

    Hopefully, this is helping to clarify. Even though we aren’t using the serveralias Andrea, you were a HUGE help in me sorting through this to a working solution. I don’t think I’ve said it yet (sorry) but THANK YOU! ??

    We’re not using serveraliases at all, so therefore the plugin is working as I expected –

    you are, you;re just unaware of it. ?? *Something* on your server points all requests for client domains, or in your case, the CNAME you gave them, to your main wordpress installs.

    that;s a serveralias.

    We’re also not using wildcard host (I believe that is only for the subdomain version and we’re only using subdirectory)

    You’re thinking of wildcard subdomain. Wildcard host is different.

    And exactly what you would use for adding 10000 domains.

    It’s all up to client to a) add CNAME (or A) record and b) add matching entry to Domain Manager.

    Right, because you either have the serveralias in place or (or maybe and) you also have a wildcard named host in apache.

    This has been done for you already by your webhost or your web team. *Something* in your server setup has already been domain so the domains go to the right place and you don’t have to park each one for your clients. That’s all I’m clarifying, so people reading along get this.

    The only reason people have to park each domain in cpanel is if they are on a shared host. that is it.

    And you’re welcome. ??

    Thread Starter ddarby14

    (@ddarby14)

    you are, you;re just unaware of it. ??

    Oh how true that usually is! I’m not tech smart, but I make up for my stupidity in determination/stubbornness. (and of course, with great people like you) ??

    Yeah, that’s why I think that using a dedicated server is what is making this tick for us. All incoming requests by default are going to this main domain. When we test this weekend on another box with 2 main domains/wp network installs and CNAMEs coming in, I expect it to blow up.

    Lesson for me (and maybe others) is small cost for extra box on cloud/extra IPs is great payoff for not managing serveraliases individually.

    You rock. ***bows***

    I’m still confused, as the plugin seems to work with users just entering their domains via the plugin (and, of course, making the appropriate change at their registrar).

    Our WordPress multisite install is set up in a cPanel/WHM account. The WordPress network is on a dedicated IP address. So, when users point their mapped domain at that IP address by modifying the A record at their registrar, their requests go right to the WordPress installation. Then, if they’ve entered that same mapped domain in the plugin, WordPress takes that traffic and sends it to their blog.

    So does our dedicated IP (and its A record) achieve what you were talking about? And do we need to do anything else? I can’t imagine setting something up for each client and each domain they want to map, as that would defeat the purpose of giving them the ability to do that themselves.

    So does our dedicated IP (and its A record) achieve what you were talking about? And do we need to do anything else?

    You’re good. ?? The server alreayd does what you need, you do not have to do anythign else.

    I’m just explaining *why* that is.

    The WordPress network is on a dedicated IP address. So, when users point their mapped domain at that IP address by modifying the A record at their registrar, their requests go right to the WordPress installation.

    And this is why it works.

    (I actually covered this in my ebook.)

    Got it, thanks!

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] domain mapping to subdirectory’ is closed to new replies.