Somethin is up with the PHP setup on the server, as the situation in the subject line keeps happening.

Different browsers, different operating systems, different computers, all the same symptom. Firefox won't just display PHP code, so it spits it out as a file download. This happens when I click basically anything on the site, including sometimes submitting a new post or thread. --but obviously it doesn't happen all the time.

 

It took four tries just to get back to this thread lol

see attached screenshot. It took over 50 clicks (I stopped counting) to get the photo attached.

If no one else here is a PHP programmer, could someone let me see the output of phpinfo(); so I can do some diagnostics myself?

 

Dude I dunno what's going on with you but I'm not having any problems at all.

 

happens on occasion, to many php based pages, dunno what causes it.... Try hitting CRTL + F5, and see if that solves it.

 

that is usually a misconfiguration with the web server - doesn't know how to handle files with the php extension. it is either that or php extensions to the web server are not installed.

this is site is running apache on linux so make sure you have the following line in your config file for apache

DirectoryIndex index.php

also make sure the config file is loading php module. the modules should be a directory of of /etc/ called apache2/mod* or /etc/httpd/mod*

anyway hope this helps.

 

Apache was crashing on one of the two web servers due to a problem with one of the modules. As the process would die, the connection would close. The crash apparently happened early enough in the connection process that Apache was not able to send content type headers to the browser. (Usually the server will say, "This is an HTML file" in a way that the browser understands.) Because it didn't get that header info, it would revert to its internal handler, which is very simple - it looks up the extension (in this case .php) to figure out what program to open it with.

You don't actually get sent the PHP source code, but it looks like you do because your browser is offering to open the content (in this case a zero-length file) for you in a text editor.

In any case, it should be fixed now.