Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:9659 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15664 invoked by uid 1010); 4 May 2004 12:22:15 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 15640 invoked by uid 1007); 4 May 2004 12:22:15 -0000 Message-ID: <20040504122215.15603.qmail@pb1.pair.com> To: internals@lists.php.net References: <20040504052554.60192.qmail@pb1.pair.com> <1083649378.20045.3.camel@linux.local> <5.1.0.14.2.20040504105411.02706178@127.0.0.1> <20040504101926.19946.qmail@pb1.pair.com> <1083666449.25843.3.camel@linux.local> Date: Tue, 4 May 2004 21:22:12 +0900 Lines: 80 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Posted-By: 202.179.19.82 Subject: Re: [PHP-DEV] nested includes fails? From: tumurbaatar@datacom.mn ("Tumurbaatar S.") I'm not familiar with Linux/Apache, but if they run as Windows/IIS pair, then I'm afraid that "php.ini" would be shared among all developers hosting on a single server and my include dir would expose its contents to other app-s. Though below may be another workaround: "Kamesh Jayachandran" wrote in message news:1083666449.25843.3.camel@linux.local... > Any reason why you want to use require_once with same filename with > different paths? > Why don't you set a include_dir as your e:\...\myapp\inc and just > require 'common.php'. > > With regards > Kamesh Jayachandran > > > > On Tue, 2004-05-04 at 15:49, Tumurbaatar S. wrote: > > 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: > > > > > > > > If a script is in the root dir, then: > > > > > > > > and if it is in other subdirs (e.g. "members"): > > > > > > > > Finally, when my script located in 'members' needs some > > include file from the "inc" dir, I include it in this manner: > > > > > > > > and I do not include "common.php" directly because > > "some_include.php" starts with: > > > > > > > > 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: > > > > > > > > > > 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. > > > >