include path problem

winey

I'm using includes in a new site, and they're working fine EXCEPT when I try to create a new directory within the root web directory and put web pages in the directory I get an 'failed opening' error for any include on those pages in the new directory. I'm assuming I need to alter the include path, but to what so that directories within the root directory can access my include path?

leland

nabberuk

i think it would be

include"directoryname/filename.php";

hope that helps.

winey

But the includes are outside the web root directory. When used in the web root directory, the same includes work fine. For example, a call to 'myfile.inc' works even though that file is not in the same directory, it's in a special directory I setup outside the web root for security.

But if I take the same 'myfile.inc' and use it on a page in a directory WITHIN the dircectory where it works, it no longer works. So confused.

nabberuk

then use the server root,

include"users/wotever/wotever/youfolder/yourfile.php";

you can find your server root by creating a php file with the following in it,

phpinfo();

then look down the page where it says server root

spcomputing_com

Or you can try a method which I use myself:

$serverroot = 'http://www.yourdomain.com/';

remember the trailing slash at the end of the domain name.

now for all of your file includes:

include($serverroot . 'includefile.php');

no matter which directory you place the files in, the includes will still work

reisve

I use this:

$path = $_SERVER['DOCUMENT_ROOT'];

and the in the include

include "$path/your_dir/from_root/file.php";

It works very well. Even on windows...

sarahk

This may be slightly extending the topic further than winey intended but I've only recently really started paying attention to the versatility of the paths.

The way I see it is there are 2 paths, the server-side path and the client-side the path.

The client side path is the path that the browser knows, based upon the URL. /images/pic1.gif is an image directly available to the browser.

However the serverside path is one I can use from any serverside script and when you have scripts that include other scripts and you don't know whether the script is ../ or ./ things can get messy.

So to be able to say

include_once("/www/virtual/mysite/htdocs/template.inc");

is invaluable. This obviously won't work from the browser but in php it's great.

An added bonus is that my secure pages are held within the "virtual" folder so I can include content from my insecure site on my secure pages and I don't get a conflict. The html that is passed out is still secure. This means that when I update logic, menus etc I don't have to copy them over to the secure site, I can go straight to testing. (Images and things called by the browser do have to be copied tho').