Upgraded two WordPresses to 3.0.4 and networked them (not to each other). All went very, very well, with one teeny-tiny glitch.
One of them works just fine with or without the “www” on the primary domain, while the other has decided that that’s a request for a rather hairy-URLed new subdomain:
“The site you were looking for, http://delanowichitacom.www.delanowichita.com/, does not exist.”
Poking about in the Apache shows they’re both configured the same. Poking about in WordPress, though, turns out that the problem child has this in the config:
define( ‘DOMAIN_CURRENT_SITE’, ‘www.delanowichita.com’ );
while the other one has its domain with no www. So I’m gonna go out on a limb and guess that that’s my problem.
Is there a simple way to work around this, or am I stuck search-and-replacing the domain in my whole database? And if the latter, is there anything weird I should look for in a networked install?
(Naturally, the screwed-up site is the one that’s got www-less links all over the Internet.)
- The topic ‘Network main site with and without www’ is closed to new replies.