A brief directory structure:
"e:\...\myapp\" - this my web apps root and it contains several
subdirs:
"e:\...\myapp\members\" - a normal, web shared subdir
"e:\...\myapp\inc\" - an include subdir where are located all my
include files and this subdir is not web shared
(though my Inetpub dir is located in C:, I use IIS's virtual app/dir
located in a different volume E:)
The above "inc" subdir contains "common.php" which is used by
all other script files located anywhere under app root and subdirs.
So if a script is located in the "inc" subdir, then it may start with:
<?php require_once('common.php') ?>
If a script is in the root dir, then:
<?php require_once('inc/common.php') ?>
and if it is in other subdirs (e.g. "members"):
<?php require_once('../inc/common.php') ?>
Finally, when my script located in 'members' needs some
include file from the "inc" dir, I include it in this manner:
<?php require_once('../inc/some_include.php') ?>
and I do not include "common.php" directly because
"some_include.php" starts with:
<?php require_once('common.php') ?>
I.e. a rule is:
a script does not include "common.php" if it includes
some other include file because that include file already
includes "common.php".
That works fine untill I included 2 and more files:
<?php require_once('../inc/some_include.php') ?>
<?php require_once('../inc/other_include.php') ?>
where each of these include files includes "common.php".
In this case, "common.php" is included in a calling script
file 2 times, even "require_once()" is used. And this leads
to a trouble.
Currently, I use absolute pathes hoping that when my app
moves to Linux/Appache, relative pathes will work normally.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
