dschaefer

Thanks for the links, they look like what I need.

It also sounds like I’m a bit too concerned about where things ought to be. It’s working now and although I don’t like the production install in the ‘dev’ directory, I guess I can live with it.

My live site is running just fine as is, I guess I wanted to clean it up so that the live site is running from the same directory that it’s published to. My assumption was that is the typical way it’s done and I want it to be right. It seems that this is a bit of a work around with WP in the dev folder even though it’s not the ‘development’ install.

I’m having a bit of a hard time finding my way around a few things like this in the install and I want to clean them up as I go.

Am I wrong in my assumptions of how things are typically done?

Thanks for the replies. I’ve got a lot of learning to do.

A test install sounds like what I need. Are there any good how-tos on this? I’ve searched and found lots of posts online about this, but most aren’t much very descriptive. I’m pretty new to this, I really need a basic step by step.

WP is generally installed in the directory it publishes to, correct? Is a good way to do this to install WP in the main directory (www.domain.com) and a test install in another directory (www.domain.com/test)? If so, how do you move changes over from test to production? Do you have to do all the work a second time? I’m assuming the two installs aren’t tied to a common database, right? That always got me in MT too, I ran a ‘test’ blog and a ‘production’ blog but never found an easy way to port changes from test to production.

BTW – on my site, WP is installed in a subfolder but publishes to the root. I’m thinking I ought to move WP to the same folder it publishes to and then install it again in a test subfolder.