To start things off :)

[Stallion]

I just thought I'd mention the possible need to use a shell-escape sequence at the top of your scripts. My server, which has a unique setup due to security risks, requires all PHP scripts to start with #!/usr/bin/php

Not a majot problem, but it took me a while to get it working as you'll need to remove it from the included files (the global duo along with the mysql data files)

Just a note to keep in mind if you're on a new server where you haven't run PHP before, and you're getting the nasty ISE's... Oh, check permissions as well :)

755 for all executed scripts!

[WebStyles]

My server, which has a unique setup due to security risks, requires all PHP scripts to start with

#!/usr/bin/php

That means your host is running PHP as a CGI, which is lame, since you don't get the performance increase you should. This also means all PHP scripts have to be in the cgi-bin, and you have to chmod them... Lame, lame, lame! Don't let your host do this to you, tell them to install PHP as a module... Or correctly, that is. ;)

[Stallion]

Well, its free hosting, due to the fact that its related to a company I work for :)

In any case, I'm being moved to a better server with PHP being run as it should, and mod_perl support should I need it...w00p!

[robot]

Who says that CGIs have to be in the CGI-BIN? That's ONLY if the apache (or whatever webserver software you use) is configured that way.

[werehere]

Originally posted by robot
Who says that CGIs have to be in the CGI-BIN? That's ONLY if the apache (or whatever webserver software you use) is configured that way.


It is quite true however that *most* PHP run as a cgi will probably have to be! That is how a *LOT* of hosts set it up.

[WebStyles]

It's also quite unsafe to run CGI scripts outside a dedicated CGI bin directory.