Support » Installing WordPress » Adding to existing website

  • I have an existing website at my domain. I would like to use wordpress to create a new website but do not want to affect my existing website while I am learning to adapt templates. Should all wordpress files and folders be in their own directory within my root folder?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Based on my experience, I do not know of any situation where (the current version of) WordPress should be installed in the root. That is because it is now possible to have the Home Page of your WordPress site appear when you type just your domain name, even though WordPress is installed in a folder. The process is documented on this site.

    I have very successfully installed WordPress in a folder and got it running “perfectly” without disturbing the current (non-WordPress) web site. You can even have multiple WordPress instances, each in a different folder, and easily switch from one to the other to run the web site from the domain name.

    Thanks adiant. I followed instructions that said to install wordpress in the root folder. Do you know whether I could simply move the files and folders into a new directory without screwing anything up?

    I just located documentation that should answer my question.

    Just wondering where that document is that you found janetmat? I’m trying to figure out if I should install in the root or not. I’m leaning towards adiant’s suggestion but wondering what the pros and cons are. I’d also like to use WordPress as a CMS as well. Any thoughts?

    bluehaus: I use WordPress as the web site delivery tool of choice for all my web sites, i.e. – I have a couple going, and will do the rest over time. It would probably qualify as a CMS, too, as I store some of the information in a separate database, then use WordPress to dig it out and present it on a web page. I had used Etomite (also Open Source) previously, but am glad I made the move.

    In short, I have never created a Post, and do things with Pages.

    At first, I began developing have one (separately customized php to access database content mainly) template file per page, but quickly saw the difficulty I was creating for myself, down the line, trying to change one piece of common code in all those template files. So, I built my own parser to look for double square brackets where I specified the name of a custom field that could exist in either the current page or the home page. Most of the custom fields have names ending in .php so I can execute php. But I also have a few other things, like html that won’t make it past the tinyMCE HTML editor that WordPress uses to let you edit Pages.

    As for pros and cons of installing in the root v.s. a subfolder, I haven’t seen any formal discussion beyond what is implied in the documentation that tells you how to run your domain name with WordPress in a subfolder:

    Part of the reason for that is that the ability is relatively new. For me, the decision was a No Brainer — always install in a folder, never in the root — because there are always “other files” in a root of a domain name, and who needs the confusion of keeping track of which is which? The folder switch ability cannot be underestimated for its flexibility to quickly switch from one WordPress to another.

    Wow thanks for the quick and very informative reply adiant! Sounds really good to me, so I’m giving it a shot and installing it in its own directory. However I am putting it into an existing site which is still in the development stage. I’m assuming once I get in to WordPress and get my hands dirty, meshing it into the entire site shouldn’t be a problem. *fingers crossed* Thanks again and I’ll keep you posted.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Adding to existing website’ is closed to new replies.