Depends on which plugin you’re using to map domains.
Thread Starter
Don
(@d_random)
I’m using “WordPress MU Domain Mapping”. Is there a plug in that can hide the primary domain?
Actually there is no need to use a plugin to map domains.
Not only will this method allow you to use subdomains without plugin, but it will also hide the primary domain from the world.
I have been using this for a while now, and it works great.
All you have to do is,
in wp-config.php, change:
from:
define( ‘DOMAIN_CURRENT_SITE’, ‘domain.com’ );
to:
define( ‘DOMAIN_CURRENT_SITE’, $_SERVER[‘HTTP_HOST’] );
Good luck.
Not only will this method allow you to use subdomains without plugin
Anyone can use SubDomains without a plugin, that’s built in.
So what is the need for even having a plug in? I try to avoid any plugins unless it is absolutely necessary.
Plugins are done by good hearted people, but what happens when they decide to discontinue their work, and the way you build your site depends on that plugin? I have learned a hard lesson with few plugins, such as wp-hive.com
wp-hive.com developer got a new job and does not have any more time for the plugin.
My advice, avoid any plugins unless it is absolutely necessary or if you are sure that the developer of that plugin will be there for a long time to continue providing updates so the plugin does not break on the next wordpress update, provide bug fixes and security updates.
You … don’t use plugins for SUB domain mapping. No one does.
The plugin is for DOMAIN mapping (like pointing domain2.com to your install at domain1.com/subsite)
That’s all.
And I pinged a couple people. Not a one of us has a clue how your ‘fix’ handles DOMAIN mapping.
Huh, am I doing something I am not supposed to?
I have 9 top level domains pointed to one multisite wordpress install without any plugins, and it works great.
Every time I create a new domain, it gets created as: newdomain.PrimaryDomain.com
Afterwards I just go to: Network Settings, sites, I click on the new domain, and in “setting” in, Siteurl, I manually change from: newdomain.PrimaryDomain.com to newdomain.com
And everything works great.
And the “fix” I gave, it helps hide the Primary domain, so it does not show up, exactly the issue original post was about.
Besides, I can’t take credit for the fix, I found it here:
http://www.wpwebhost.com/2010/06/simple-domain-mapping-without-any-plugin-in-wordpress-3-0/
No, but for a BRIEF moment you were confusing up subdomains and top level domains 😉
I had not seen that article on domain mapping before, though! Thanks!
It’s not what we call “best practise”. and the guys who work on the domain mapping plugin, one of them works for Automattic.
I’ve got WPMU setup and all is working as per the following redirection (both with the method above, and with the publicly available domain mapping plugin installed):
http://www.subdomain.mainsite.com redirecting to WPMU blog: blogsite.com/subdomain_blog
I have parked the domain: subdomain.site1.com in plesk onto blogsite.com
I want to keep the domain name base: http://www.subdomain.site1.com during the whole redirection. How can I achieve this – as at present, using either method – the url in the browser switches to: blogsite.com/subdomain_blog
Thanks.
I’ve got WPMU setup
Are you running WordPress MU (last version was 2.9.2) or WordPress (3.0 or newer)?
Yep, it is: WordPress 3.2.1.
More testing, so bit more to describe.
1. I only get above functionality with WordPress MU Domain Mapping plugin installed.
2. The redirection does actually seem to keep the url: i.e. http://www.subdomain.mainsite.com on redirection – up until any links are clicked – as all hyperlinks (and page url’s) are blogsite.com/subdomain_blog format – and are not relative to original domain.
Am I right in thinking that these domain mapping plugins are really designed for mapping a wordpress.com subdomain (e.g. xyz.wordpress.com to a new domain xyzdomain.com). It’s like I’m trying to do it the other way round – i.e. I’m attempting to collect blogs that are essentially on separate domains under one WP network – but make it appear that blogs are still all on separate domains.
It works *similar* to how they do it on wordpress.com – because of course, you canot add plugins there. 😉
There’s a checkbox in the domain mapping plugin about redirecting to the original blog address.
Also, it could be how you pointed the subdomain in plesk (which is my guess where things went wrong).
1. I only get above functionality with WordPress MU Domain Mapping plugin installed.
We haven’t renamed the plugin because people would lose track of it in terms of getting updates. For the same reason, the plugin slug isn’t changeable.
There’s a checkbox in the domain mapping plugin about redirecting to the original blog address.
I’ve looked through all admin screens I can locate, but I’m not sure which checkbox you are meaning.
These are the main options in domain mapping:
# Remote Login
# Permanent redirect (better for your blogger’s pagerank)
# User domain mapping page
# Redirect administration pages to site’s original domain (remote login disabled if this redirect is disabled)
# Disable primary domain check. Sites will not redirect to one domain name. May cause duplicate content issues.
I’ve tried several ways of setting up the dns on Plesk including following all instructions in this article:
http://davidlaing.com/2008/07/24/domain-mapping-with-wordpress-mu-plesk-apache2-ubuntu/
When I follow these instructions some other domains of mine on the server are also redirected to the new domain for some reason. It doesn’t work any better than just setting up domain parking (to blog.wp3domain.com) on the WP3 network domain – which doesn’t affect the other domains on the server.
Ron, I presume you mean that it’s not possible to alter default folder names in the plugin? Just to confirm, all is set as default – and that I am utilising this plugin: http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/
To clarify, the browser is being directed to wp3install.com/blog from blog.originaldomain.com – except the browser is now in a very different place – url (inc. all links) and no longer in the name space of the blog.originaldomain.com
