Domain mapping issue


  • MrCheck

    I would like to allow my customers to use own domains for their blogs.

    When I enable the "Domain Mapping" plugin the user is able to select a custom domain as alias domain for his blog. It works very fine, but I have one little problem:

    When I enter http://www.example.com as custom domain, it always discards the "www" and only uses example.com. Can you tell me how to use the www subdomain as custom domain?

    Thanks a lot in advance!

  • aecnu

    Greetings MrCheck,

    Welcome to WPMU DEV!

    Thank you for letting us know about the items you are dealing with in your WordPress installation.

    In this case it appears that you have some misconceptions on how this works and just to make it clear that to WordPress MultiSite the www. is considered taboo in sub site names i.e. http://www.mymaininstallationdomain.com but coolness.mymaininstallationdomain.com is fine and correct and should resolve.

    Now bring in Domain mapping and this is where you map a TLD (Top Level Domain) to one of those sub sites and once comple and propagated will resolve to the TLD using either the www. or not with www

    Please advise if this helps and if not then we need to start at the top on this one tracing out the domains first - in this case please post the URL to the sub site and the domain you want to map.

    Please advise.

    Cheers, Joe

  • MrCheck

    Hi aecnu,

    thanks for your fast reply. My problem is the following:

    Let's say my network's main domain is wpnetwork.com. Normally, every blog would get a domain like customer.wpnetwork.com. Now the customer wants to use his own down domain (let's say customer.com) for his blog. He wants the FQDN http://www.customer.com as main domain name for his blog. When he uses the Domain Mapping tool and enters http://www.customer.com, the plugin changes this value into customer.com.

    Do you understand my issue? It's not possible to use the customers own domain with www - in the meantime I've installed "WordPress MU Domain Mapping" plugin and this one does what I want :smiley:

  • aecnu

    Greetings MrCheck,

    Thank you for letting us know and absolutely I understand the issue with your clarification and happy that you found a solution to meet your needs.

    I too have used Donncha's Domain Mapping plugin in the past and the reason why ours is constructed a little different is to include Pro Sites integration.

    Happy to see you have this resolved to your satisfaction.

    Thank you for being a WPMU DEV Community Member!

    Cheers, Joe

  • aecnu

    Greetings MrCheck,

    Thank you for your additional input and question.

    Though Donncha has indeed chosen to do so, I do not see a way to convince our lead developers to go against the intended use and creators of WordPress themselves.

    Please note in the WordPress codex:
    http://codex.wordpress.org/Before_You_Create_A_Network

    Especially paying attention to the creators very own graphic of how the MultiSite network should be configured:
    http://codex.wordpress.org/images/1/13/sites-edit-site.png

    Notice the omission of the www?

    Based upon the absolutely clear indicated intended use and network configuration as dictated in the WordPress codex, what is a support staff member to do? Go against the creators indicated intended use?

    I am supposed to support this type of action?

    Personally I find nothing wrong with it (www) though also personally believe only complete morons/idiots need www in a domain.

    If they do not know by now that a domain name is inherent to the world wide web (www), they should box up their computer and take it back to Walmart and forget about it - but that is me.

    Professionally it is obviously against the codex and therefore I am unable to support the action - while at the same time I will put it in for a feature request and let the developers/coders make the final call on this.

    Have a GREAT upcoming New Year!

    Cheers, Joe

  • MrCheck

    Hi aecnu,

    I've read this page and it says:

    "Each site has a different domain. For example: example1.com, example2.com, site1.example.com, site2.example.com."

    A domain may include a subdomain. WordPress knows it, I know it, and you should know it too. When a customer would like to have a shop at shop.customer.com and a blog at blog.customer.com everything is fine. Why shouldn't he be able to choose http://www.customer.com - it's a subdomain like everything else.

    Even with your plugin subdomains like site1.example.com are possible (which is against developers intended use in your opinion), even shop.example.com is possible, but http://www.example.com is not because only idiots need an www? Thats ridiculous :slight_smile:

  • aecnu

    Greetings MrCheck,

    I really appreciate your input and indeed it has been fun exchanging perspectives with you - and I certainly thank you for that.

    I have indeed submitted this ticket to the feature requests area which is/was the right thing to do so since this is the only possible resolution to this item of adjusting the WPMU DEV plugin to facilitate the www.

    I have not typed in www in years ... lol

    Have a GREAT upcoming New Year!

    Cheers, Joe

  • Zyniker

    Of curiosity, has anyone tried this as a workaround:

    http://wpms.com/ <-- root install
    http://mapped.com/ <-- mapped domain

    Use Multi-Domains to add http://mapped.com/ to the WordPress MultiSite install at http://wpms.com/ and then create a subdomain site on http://mapped.com. Create that subdomain as "www". All that would remain at that point would be to redirect traffic from http://mapped.com/ to http://www.mapped.com/ via .htaccess (or some similar method).

    I just attempted this on one of my test installs and it seems like everything worked and is currently functioning. Is anyone aware of a downside to this?