i know this has been brought up before, but here are a few good reasons to
add .php to the end of all the module files:
1. security - at least 5 times now i've been able to find out people's
db name/login by requesting the "/modules/include/global_settings"
file. without an extension, most servers send it as text. easily
fixed, but it doesn't seem good to have FT install with such a
big security hole.
2. file transfer - lets ftp clients know to use text or binary, etc.
3. syntax coloring - lets editors know what type of code is in the file
so that they can color it correctly.
4. file type - on mac and windows you can tell the OS what program you want
to open the files with if they have an extension (on windows it uses
the actual extension, on mac it adds creator info when you
ftp/untar/checkout the files).
we could add a function that wraps include() and adds the file extension, so
that if the extension ever needs to be changed/removed it won't be all
through the code.
like:
ext_include ($file)
{
include($file . ".php");
}
could maybe also do the double-include checking in that function.
- isaac =)
|----------------------------|\ | | | /|----------------------------|
Isaac Reuben | \| | |/ | [EMAIL PROTECTED]
-------------------------
"Maybe she's just pieces of me you've never seen" - Tori Amos
|-------------------------------------------------------------------|
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
