Click to See Complete Forum and Search --> : File Extensions


SuzanneB
07-10-2005, 04:40 AM
I have a few sites that use PHP extensively.
I have been a bit unhappy with my host recently, because their servers are a little bit slow, so I have been trying out a new host.
So far there have been no problems at all, well, with the exception of one fairly small problem. The new server bans the use of .htaccess because of some security issue or other. Now ALL of my files contained a php include, which means of course that they need to be renamed to .php because I can’t change what the server sees as a file that may include php. That’s not a problem with 99% of the files, but it is a problem with index.htm. Of course if I rename that one, then it stops working. Now I can think of a solution to that problem but I don’t like it much. Basically get rid of the include and php in the index.htm and hard code it. But clearly this is not very nice. I wanted to ask the community here, which do they consider to be the best solution.

bathurst_guy
07-10-2005, 05:08 AM
I spose you could have index.php and on index.htm just redirect it to index.php if thats allowed. Your new host is very strict! lol

SuzanneB
07-10-2005, 06:41 AM
I get pissed off with hosts. Every one has some stupid problem of other, but you never find out until you have paid the money, then it's too late. The worse part is all this takes time. We could have the damn site running in days, except weeks is spent messing about with the host.

SpectreReturns
07-10-2005, 05:13 PM
If you have access to httpd.conf you can make the server look for index.php, or make .htm parse as php.

bokeh
07-10-2005, 06:18 PM
the server should automatically open index.php but usually index.htm and index html take priority. Remove any file named index.htm or index.html and it should work ok