Remove index.html. It’s just going to cause you no end of grief.
Instead, I would suggest a static front page for your WP install
http://codex.wordpress.org/Creating_a_Static_Front_Page
if you absolutely must run the index.html, then run that in your root, and move wordpress to it’s own subdomain/folder
RVoodoo, I didn’t get you mate.
I put index.html & index.php in the same root folder. Can you please explain how can I do it?
You don’t. It breaks things, and not just WordPress. Your server is meant to handle ONE index.* file as the main root. WordPress assumes that it’s the root, so you’d either have to re-code WP to look for /index.php instead of just /, or …. you get rid of index.html, make a static front page, and be happier.
i think rvoodoo is saying that for example if you want a static page for your home page (index.html) then you should put your wordpress files in a sub folder, like “blog” for instance.
if you have an index.php and an index.html in same folder it can cause all kinds of problems and ipstenu is saying that you don’t need an index.html at all as you can make static pages in wordpress and use them.
i hope that clears it up for you.
I was thinking the same. Sad to know WordPress doesn’t allow an index.html file whereas forums never give such problem.
Static Page ain’t a good option since, it gives the same stupid theme as the background.
Anyways, thanks for the help guys!
It’s nothing to do with WordPress. Or rather, yes, WP COULD specify ‘/index.php’ at the end of their URLs, limiting your ability to customize your blog to your heart’s content.
More it’s how web servers work.
Static Page ain’t a good option since, it gives the same stupid theme as the background.
You can totally customize your template of the static front page to be anything you want, you know. It’s just themeing 🙂
