Just a reminder that PHP6, soon to be released, will not allow Register Globals at all, whatsoever, so you are better to learn to code without using Register Globals = on.

Also, with resect to the single dot and double dot method of addressing a file:

This syntax is a left-over from the days of DOS Operating System where a single dot meant "this directory" and the double dot meant "file's Parent Directory", so good programming practice would use the single dot syntax for a file in the Current directory ( include './filename.ext' ) and double dot syntax for the Parent directory ( include '../filename.ext' ) You can travel to several levels of Parent Directories by adding sets of double dots, too. ( include '../../../../filename.ext' ) would go back 4 levels.
Similarly, a slash without the dots is used to indicate the path to the file starts at the Server Root. ( include '/filename.ext' )

http://www.hardcoder.com/scripting/php/include_files.php

 

 

 

Comment/Reply (w/o sign-up)

Thank you for pointing that out. I was confusd and always thought that ".../" meants two levels up. I will try this soon once I get back to working on my PHP project.

Comment/Reply (w/o sign-up)

It is also a good coding method to practice isolation between Global Variable and Local Variable.

Comment/Reply (w/o sign-up)

I had no idea! so the basic concept is if the file is in the same directory of the operating page, jsut put ./filename.ext, but say its in root/file/ and your operational page is in root/file/file/ using ../filename.ext would allow it to work, correct?

 

 

 

Comment/Reply (w/o sign-up)

Actually, Unix uses this too. And Unix is a lot older than DOS. Unix, last i checked, came out in 1969.

But to add to your other statement: When you include the root directory by including a forward slash in the beginning of the file path, this does not neccesarily mean your "public_html" folder. It means the root of the system itself; assuming the system is a Unix-based system; other systems may be different.


Assuming i understood you correctly: Yes, that would work. But it is a security flaw if you allow ../ in _GET variables without verifying the extension.

Comment/Reply (w/o sign-up)

no I didn't a problem like that because I don't use php too much and by the way many suggestions have been already given,so you may try ny one give in this thread,I know these t17 members are really far more experienced then I am,so I am not suggesting anything because I may suggest something wrong.

Comment/Reply (w/o sign-up)

I never have had this problem. Of course I have all my files in the same directory at the moment, but my PHP includes work fine and I use the $_GET variable on some of my pages.

You can check it out at my site.

http://ninfanzone.uni.cc

I am using PHP include to get my CSS into my pages and for the menu at the top.

Comment/Reply (w/o sign-up)

yeah, as long as you use Include($_GET['blah.php'] you won't have the problem, or it could be the difference in what you are includeing , (visible/css style) content

Comment/Reply (w/o sign-up)