WordPress MU

I'm having trouble installing WordPress MU so it will work in both our testing (test.foo.com) and our production (www.foo.com/blogs) environments.

I'd like to be able to copy the production database and files from our production into the testing environment, make changes to the files, test the changes, then move the files from testing to production. The snag I'm running into is the particular domain name (www.foo.com) is all over the database and won't work on test.foo.com.

Is there a way to configure WordPress to be domain neutral, i.e. "/blogs"?

Thanks for your help!

Just for reference, please make sure you install it in foo.com. http://www.foo.com will cause you issues.

I'm a bit lost here as you don't say where the user blogs are coming off of so i can't really give an answer. If you;'re going to do user.test.foo.com, then you;re going to hit an issue with foo.com/blogs/user as you're going to be going from an install setup for subdomains and then over to a setup for subdirectories.

You can't set it up to be domain natural although you can set it up for multiple domain installs.

Well, now that I say that, I wonder if you could empty out the domain out of the wp_site table and just leave in the path. You'll have to edit out a number of other tables though.

It's a thought.

Thanks for your reply, drmkike.

My production environment:

http://www.foo.com/blogs/user

My test environment:

test.foo.com/blogs/user

It sounds like nobody is using a system like this. I need to go into the scripts, I guess, and see how much code I need to modify. Hopefully not too much!

P.S. I haven't run into any problems so far hosting on http://www.foo.com instead of foo.com. Should I be worried?

my dev env. is a totally separate MU install.
my test env is a separate MU install, but uses the prod main DB (i have a setup with plenty of separate MU installs using the same main DB). So basically it's a test blog, running on the same domain as the others, but which has a separate proxy rewrite rule that routes the request to the test env. instead of one of the prod ones.
When i have a new func. ready there, i have an rsync script to push it to prod env.
I'm working on a CVS checkout + rsync push so that i can push things directly from CVS to test/prod.