Accidentally killed PHP

Portal Home > Knowledgebase > Articles Database > Accidentally killed PHP

Posted by aodat2, 08-08-2010, 10:50 AM
I'm not sure what I did but I was actually installing a Webmail Client and I guess I must have done something to do with the PHP because after I got the Webmail Client done, the PHP on my server just didn't like me anymore. Anytime I click on any links or etc on the server which has a .php extension, I will be prompted to either Save/Open. Can anyone tell me what in the world did I do wrong? What happened in between and why am I getting things like that? I've just started meddling with Windows and I'm already getting a headache. Oops.. forgot to mention... server is running on IIS. Please help! Last edited by aodat2; 08-08-2010 at 10:57 AM.
Posted by aodat2, 08-08-2010, 11:24 AM
I think I know what I did wrong. I clicked on something called as "go-pear.bat" or something like that. Now... it seems that I can't undo it or something. Please... if anyone knows what to do, please help.
Posted by tix3, 08-08-2010, 01:56 PM
Please give some details such as the OS and webserver.
Posted by Interix, 08-08-2010, 02:00 PM
bat = Windows.
Posted by aodat2, 08-08-2010, 03:25 PM
Oops... so sorry. Thought I included it into my previous post. Windows 2003 Standard IIS 6 PHP 5.3.3 It just seems that any and every file for example filename.php which is on IIS which you click on will just come up with a Save/Open link instead of showing up as a page on the browser. I have tried uninstalling and reinstalling PHP but the same thing is still happening. Still can't do much. It was totally OK before this and now, well... I can't do anything even if my life depended on it. Do help if you could.
Posted by xmlxp, 08-08-2010, 06:18 PM
i had same issue before http://www.webhostingtalk.com/showthread.php?t=967712 try to browse your website from proxy if its working ok then its a caching problem. whats your website link? Last edited by xmlxp; 08-08-2010 at 06:22 PM.
Posted by aodat2, 08-08-2010, 10:37 PM
Totally 100% sure it's not a caching problem. It's some configuration which went off. I'm sure of that. Caching would not cause EVERY PAGE to come up that way.