I already have an index.html site up an running. It is simple with css in one subfolder and images in another. I want to install and implement WordPress 3.0 over time in the same root folder as the original html solution. I have already tried it but I had to delete WordPress because when I tried the domain in the web browser it came up with the WordPress start-up page. What I want is this: I have index.html (the original) in the same folder as index.php. I decide to let people that will visit today’s solution http://www.mywebsite.com to be directed to the index.html file and not the WordPress site. While people use the original website my intention is to build up my wordpress site to give it a new look and to test out things. When everything is ready I will delete index.html and go live with it.
I don’t know what is the best way to do this. Maybe someone can give me some advice? Is it better to install WordPress in the same root folder as the original or do I have to install it on a subfolder (like http://www.mywebsite.com/wordpress/ to prevent the conflict between index.html and index.php. If I chose the latter solution will it be relatively easy to move the entire site to the root afterwards?
- The topic ‘How to prevent Index.php override index.html’ is closed to new replies.