The base URL is the root directory of your WordPress site. By changing that in WordPress, you’re telling it to look to the new location. But using the menu option won’t relocate your install, you’ll need to do that first.
There is guidance on this here: http://codex.wordpress.org/Moving_WordPress#Moving_WordPress_Multisite
Sorry, I’ve misstated what it is I actually want to do.
I have domain mapping and use various domains with my blogs–in the following forms:
http://dom1.com <– primary install of wordpress
http://dom2.net
http://abc.dom2.net
http://xyz.dom2.net
http://another.com
http://one more.net
All domain names point to the one folder on my web host.
Problem is anyone logging in on dom2.net is redirected to dom1.com for that and sent back. That’s one of the problems I want to address (I know there’s another option to keep the user local, but that’s not ideal for other reasons).
There’s an option under “my sites” to select the primary domain for the wordpress install. Technically the db isn’t moving, just the pointed URL for back and front end stuff. Just to clarify, all the URL’s point to the one web server’s folder. I just want the primary domain to be dom2.net now. So these logins are within my main network of sites.
I’m pretty confident this setting iswhat I’m after and what I need to change. Just not 100% 🙂
I hope I’m more clear in my intentions now. The setting I’m talking about is the primary domain and so my question is, are there any tricks, tips, problems with changing this ‘willy nilly’
Ok, I just went looking–still not prepared to experiment just yet…
What I’ve just realized is that this option to change the primary domain is only available in the subdomains themselves, not in the network admin.
For each blog, the primary domain is http://dom1.com (regardless of the blog).
For the first time ever, I just opened the drop down and what I saw wasn’t what I expected. With reference to the URL’s I provided above, the drop down (for example in the case of dom2.net) is
http://dom1.com <– current setting
http://dom1.com/dom2
http://dom1.com/abc
http://dom1.com/xyz
http://dom2.net
http://dom1.com/another
http://dom1.com/onemore
I’m assuming the dom2.net appears, appears as a result of domain mapping elsewhere.
The line dom2.net is different in each blog, and the URL for each blog appears in this spot
So maybe this option doesn’t do what I was expecting. I’m not too sure now…
No that option will nt help at all with what you are trying to do.
For the mapped domains, do you have “remote login” checked in the domain mapping options on EACH sub site?
Look under subsite -> tools -> domain mapping.
I have turned on (and off), tried both ways with that option you suggest. In some ways, remote login OFF is better for the user experience, but a PITA for me. But what I did find, that although this is under SITE administration, changing it ANYWHERE affects all sites. ie, I had it on in all sits, turned it off in one, and went thru the others, and they were already turned off. They were all turned on initially.
So, back to that option under “My Sites”, what is it for? There’s little I’ve found for it. I was going to play with it for one of my lesser blogs, I still might. But don’t want it stuffing anything else.
My basic intention is to go from using dom1.com as my main admin site to using dom2.net. Because this will give the users the most streamlined effect–I want to integrate facebook (as per other topic), but I don’t want them EVER seeing the old admin domain. I’m pretty sure they won’t, but I want to be sure.
