Everything was going great until I added AddHandler application/x-httpd-php5s .php towards the .htaccess file during my local server's document root (that we change frequently with respect to the site I am dealing with). Since I Have did that after I visit http://localhost:8888 my browser just downloads the index.php and it is not processed whatsoever, only the raw code. Now I removed that line in the .htaccess file but I am still getting this issue.

I have discovered that basically add an alternate admission to my hosts apply for 127...1 the brand new entry reacts like 'localhost' accustomed to. But when I add the road above to my .htaccess it knocks out that new host too. I have attempted re-installing MAMP and clearing its caches and all sorts of the temporary files I possibly could find. I surfed through Apache's httpd.conf file routinely without success.

So, to become obvious: http://localhost:8888 is going through the above mentioned problem. Basically give a new admission to my hosts apply for 127...1, say 'goomba' and also the above lines are not within the root .htaccess (and it has never been for your host/alias/whatever) i quickly can access http://goomba:8888 all right. But when I actually do include that line towards the .htaccess then I must add another admission to my hosts file to obtain around it even when I remove that line in the the .htaccess file.

I am fine with utilizing a different 127...1 alias (host? what's that known as?) but it is annoying me this continues to be damaged.

Simply to be obvious, I am on Mac OS Leopard (but I am not while using built-in Apache setup, but MAMP).

Possibly you would like application/x-httpd-php5 rather than application/x-httpd-php5s? (Note the possible lack of an s in the finish.)

You're using a mimetype in which a handler ought to be (see documentation on handlers)

Do this rather:

AddType application/x-httpd-php5 .php

EDIT: As you've indicated caching modules are loaded, you can educate yourself on caching and htcacheclean (to obvious the disk cache). You may also temporarily make use of the CacheDisable directive. Another factor you could likewise try would be to relabel the file you have asked for (e.g. index.php -> index.bak), request the file again within the browser (should now 404), then revert and check out again.

First see if your apache server is running. Start->Run->cmd after which execute command:

netstat -abn

Research the end result for line such as this:

TCP ...:8888 ...: LISTENING 600 [apache.exe]

Should you cant find anything listening on port 8888 ( number..:8888 line) your apache is neglecting to start. To discover why it cant start you need to find apache log directory and look at the mistake.record (might be you've up-to-date your php resently?). If you discover ...:80 listening line however, many other software programs are listening there (have you got IIS running?) then you definitely should remove / reconfigure that softure to free port 80. For those who have apache listening on port 80 but nonetheless cant open your website and also you cant evaluate which is leading to the issue via analyzing apache log files it my be database problem. See if your mysql is running and listening using same command but you ought to be searching for

TCP ...:3306 ...: LISTENING [mysqld-nt.exe]

Should you cant find such line your mysql server isn't running - check mysql log files for errors. If both servers are running and also you cant have any output inside your browser then look at your firewall and anti-virus - they might block your demands. Hope this can help )

For the similar problem, i removed the '5' AddType application/x-httpd-php .php .htm .html

its working fine! try