Log in

View Full Version : Firefox wants to "run" my index.php instead of display it



kuau
02-06-2008, 06:51 PM
Because GoDaddy doesn't allow .htaccess files, I had to rename the index.html to index.php instead. This is not a problem in IE, but if I try to open the homepage in Firefox, it thinks I am trying to run a php file and asks me what program to use.

If I type the full URL (www.mauiunderground.us/index.php) it works, but if I just type the domain name the way most people do, it tries to run the file. The only time I've ever seen this happen before was when I tried to use an .htaccess file, but there is no .htaccess file!! What is going on?? Thanks.

www.mauiunderground.us

boogyman
02-06-2008, 07:41 PM
it means the server cannot run the process the file, so it gives you that popup screen.
This can sometimes be caused by the server being down at the time.

I am not experiencing any problems with accessing that site on Fx 1.5 or Fx2

james438
02-07-2008, 01:01 AM
godaddy allows htaccess files. I use htaccess on my site without any problems that I can think of. If I remember correctly the problem was that it was not recognizing files with php extensions under configuration 1.0. I don't think you can even get configuration 1.0 on their linux server anymore and 2.0 is default. When I converted to configuration 2.0 I did not have this problem with htaccess anymore.

Don't quote me on that because it has been a while now since I fixed that problem.

EDIT: I read on another forum that this is indeed the case http://forums.digitalpoint.com/showthread.php?t=440274

kuau
02-07-2008, 07:39 AM
Dear Boogey: I just tried it again and got the same message. Here it is...

http://www.mauiunderground.us/file-anomaly.jpg

I couldn't figure out how to add an attachment so I hope this image shows up. I am using FireFox 2.0.0.11. I thought my computer might need rebooting but that didn't help either. Thanks for checking. Could it be something on my computer causing it? Am I the only one it is happening to? erin :)

kuau
02-07-2008, 08:27 AM
Dear James: Well that is very interesting because GoDaddy tech support sent me this on 1-29-08:

Thank you for contacting Online Support. Unfortunately you will not be able to parse PHP in HTML files. You will need to use the extension .PHP. We do apologize for any inconvenience that this may cause you. Please let us know if we can assist you in any other way.

Regards,

Felicia B.
Online Support Technician
Customer Inquiry

Dear Nathan: OK, great, thanks! My other question is: How do I get apache
to parse .html files the same as .php files so that I don't have to use all
..php extensions in order to use php includes? This is the .htaccess file I
use successfully on Powweb, but it doesn't work on GoDaddy:

Options +Includes
RemoveHandler .html .htm
AddType application/x-httpd-php .php .htm .html
ErrorDocument 404 /html/404.html

Does GoDaddy not allow this? Or is it done some other way for GoDaddy?
---------------------------------------------------------------
And that is the very .htaccess file that caused the above problem. It definitely didn't work. So I believed Felicia, deleted the htaccess, and renamed all my files to .php

I just tried an .htaccess with "AddHandler x-httpd-php5 .php .htm .html" from that other forum and it didn't work. I'm supposed to be on a Linux server - how do you tell? This is driving me nuts. Thanks for the info - at least now I know it is possible on GoDaddy even if their tech people don't know about it. I must say I have found GoDaddy's tech support to be less than helpful. Online info re .htaccess files seems to be inconsistent so it is really difficult to know what is the definitive way to state the commands.

Mahalo for your help. Aloha,erin :)

jscheuer1
02-07-2008, 04:15 PM
No problem here with:


http://www.mauiunderground.us/

in FF. Might be a configuration issue in your copy of FF.

rpflorence
02-11-2008, 02:48 AM
Works fine for me to. FF in OS X.

kuau
02-11-2008, 07:56 AM
Dear John & RP: Thanks for checking. I just tried again and now it is working! My FF auto-updated to 2.0.0.12 on Friday but that didn't fix it. I have no clue why it suddenly is working, but I'll take it! Mahalo for your help. Aloha, erin :)