WordPress MU

currently the main "master" blog is setup like this: http://my-domain.com
However, when we add "www" it the blog goes into a "redirect loop" courtesy of firefox.

What is wrong here? Something in .htaccess?

We prefer it to be www.

WPMU is designed not to work with www (www being a subdomain). There are several threads on here about how to work round it and make it work with www.

Hi Steve, Thanks for the response.

Can you point me in the right direction? I wasn't able to find anything that helps, most seemed to describe "clearing cookies" which wasn't the issue.

A quick search using www as a term finds a post which links to:

http://wpmututorials.com/hacks/forcing-mu-to-use-www/

Thanks Steve!

http://wpmututorials.com/hacks/forcing-mu-to-use-www/

Thanks, Steve, for the link, but that doesn't seem to work with the latest version of WP MU.

I've tried it a few different ways and I can not figure out how to make 2.8.6 use the 'www.' successfully.

There seems to be two approaches. First, install it without the 'www.' and then change instances in the database after install. Second, change the install file so that it installs correctly, sorry, I mean "the way I need it to install", with the 'www.'.

What changed in 2.8.6 that I need to address?

It;s still hardcoded in a few places to absolutely strip the www for soem requests. So even if you can initially get it to respond to the www, you're still going to have to make sure the server will show the site without the www.

I had the same problem testing it tonight. I had to undo the change as it wasn't working...perhaps you might update that blog post :)

Considering the date on the post, if I went back and edited every single post on my blog to be full of current information, I'd be editing posts for literally weeks.

In more recent posts, I have specified the version it applies to. The reason I haven't made a new post with how to do this on recent versions, is because it is very hard to. See above where I said it still strips the www.

Set up your server to send all www requests to the non-www. It's a heck of a lot easier to fix.

(this is one issue that will be taken care of post-merge)