On Tue, 17 Aug 2004 10:42:50 -0400, Gryffyn, Trevor wrote:
Hi Trevor.
a short note ...
>Maybe not the most elegant, but I like to keep my stuff kind of modular
>so what I've done is just create an "includes" folder in the root and
>them reference it as include("../includes/includename.inc") from
incompatible.php
Just my 2 cents in the hopes that it helps someone.
David
-Original Message-
From: Gryffyn, Trevor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 9:43 AM
To: [EMAIL PROTECTED]
Cc: neil
Subject: RE: [PHP-WIN] Re: include_path and relative vs. absolute paths
M
-TG
> -Original Message-----
> From: neil [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 17, 2004 8:31 AM
> To: [EMAIL PROTECTED]
> Subject: [PHP-WIN] Re: include_path and relative vs. absolute paths
>
>
> Thanks John
>
> That is a great solution, well at
Thanks John
That is a great solution, well at least for my development box where I can
control my php.ini. The jokers who host one of the sites I look after have
the include_path pointing to a non-existent place and won't modify it.
Thanks anyway
Neil
"John Lim" <[EMAIL PROTECTED]> wrote in mess
Good question. I had the same problem when i switched from .asp to .php
Suppose you want to use relative paths, eg. reference child1.php from
file1.php, where the file locations are:
path/file1.php
path/child/child1.php
The trick is to generate an absolute path for the current file, and find
Hi Neil.
The require and include family of constructs are 'able' to read absolute
paths, but the resolve the paths as local physical paths on the filesystem,
and not as absolute paths by the virtual root.
--
Running 'ojtibi' on '127.0.0.1' (BATCH_OPTIMISTIC mode).
"Live free() or die()."
--
P
