QUOTE:
Will there be a bug-fix in the next version?

Fixing the .htaccess file is a step all should take when installing, I don't know if it's a bug in the script though-Dewed?

Ouch my head hurts from this one... I do beleive that this is most likely the most commonly asked question...hence the FAQ.

It can be an easy fix or not but the fix is always adding the correct code in the .htaccess file.

Do remember that the guts of the Dew-NewPHPLinks script runs using the directory script, it's a file not an actually folder...that is in fact confusing.

Worked for me. Thanks!

I'm on Hostgator running Apache 1.3.41. Using the Apache links and your "hit it with a club" method, I figured out that mine is supposed to be as follows:

<Files directory>
#ForceType application/x-httpd-php
#SetHandler application/x-httpd-php
SetHandler application/x-httpd-php5
#ForceType x-httpd-php
</Files>

It took a couple edits and uploads to get it right, but it DOES work.

Glad to hear the http force worked for you!

I'm now trying to get a local copy of my Mac running Leopard to work so I can make changes without uploading to my server.

I've got Apache 2.2 running on the Mac, but no matter what I do to the .htaccess file, nothing seems to work. Any ideas?

Check the httpd.conf file (the Apache config file )

If you see a line

AllowOverride None

then no directives in .htaccess files are honored..

you could change it to

AllowOverride All

to allow all directives in .htaccess

See http://httpd.apache.org/docs/2.2/mod/core.html#allowoverride

but.. since you do have access to the httpd.conf file, you can put the directives there,
instead , and keep .htaccess files ignored.

<VirtualHost>
ServerName www.mysite.com
DocumentRoot /var/www/html/username
<Directory /var/www/html/username>

- - - - - - -
- - - - - - -
- - - - - - -
</Directory>
<Files directory>
ForceType application/x-httpd-php
</Files>
</VirtualHost>

Note apache needs to be restarted for changes to httpd.conf to take effect..
how to restart it depends, I'm old and school command liner..

server httpd restart

or you can determine the parent proccess ID (PID) like ..

ps -aux |grep httpd

that should spit out the PIDs Apache is using, normally the lowest number is the process that needs restarting.. sticking to the caveman approach, hit it with a club

kill -HUP XXXX where XXXX is the lowest PID you found


For info on further Apache tweaks see ... http://httpd.apache.org/docs/2.2/howto/htaccess.html

I gave up on it. Who installs a script on thier site expecting to have to go fool with htaccess etc? Bugger that.

Spot