Problems with "require" and "includ

[Anon]

Hi folks

In my php-code I use the commands "require" and "include" to read external files with connection-datas for my database. With Linux and PHP everything works fine. Now I have to port this code to a windows NT machine with PHP 3 and here the problems starts, because the following error message occurs :

with require:
Failed opening required 'conn_data.php3' in D:...

with include:
Failed opening 'conn_data.php3' in D:...

The path is ok.Is there something I have to change in the php.ini file or what can help ????

THX

[[deleted]]

Apperently the path isn't ok. If it was, the file would be included.

Are you accessing the file through a full pathname of through the include_path?

[ayzee01]

Try using relative paths i.e. include ("../includes/soming.class.php");

[[deleted]]

relative paths in include files are a no-no.
It says so in my little black book.

[ayzee01]

no you nonce.

dont put relative paths inside your include files.

Rather, reference them from the page you want to include them in using relative paths.

i.e. include ('../../includes.php');
Read my original post would ya.

Also, make sure that you have a directory named tmp in the root of your boot drive (i.e. C:\tmp for win) as this is the default temp directory specified in php.ini and you will more than likely generate an error when trying to include files if you don't have that dir.

This method has several advantages such as not having to redo hard coded links if you move or add a page and you can make a directory secure and store the includes within that so no body can get to em.

black book?!?!? <snigger>

[[deleted]]

"dont put relative paths inside your include files."

that's what I said, you nonce.

"Read my original post would ya."

which one, you only replied once. and it said:
"Try using relative paths i.e. include ("../includes/soming.class.php");"

wich is a bad idea.

"Also, make sure that you have a directory named tmp in the root of your boot drive (i.e. C:\tmp for win) as this is the default temp directory specified in php.ini and you will more than likely generate an error when trying to include files if you don't have that dir"

That is new to me. How does the lack of a tmp dir influence an include command?

"This method has several advantages such as not having to redo hard coded links if you move or add a page and you can make a directory secure and store the includes within that so no body can get to em."

Relative paths are the first to cause problems when things change.
It is much better to define the locations of the files in constants at the top of the script or use an include file whose location does not change.

[ayzee01]

Right back at ya.

(nonce).

Firstly, the tmp dir issue.
This happened to me a few months ago after installing apache under a win32 environment.

As soon as I had created the tmp dir (which is phps default include dir), the problem went away. (and no i wasnt referencing the include from the tmp dir)

Secondly, the argument with include files and relative paths could probably go on until this thread is so long that it would take forever to read.

So lets just say that you have your opinion (however flawed it may be :o) ) and I have mine.

Leon.

[[deleted]]

Lovely this name-calling. Get's a lot of frustration out of the system doesn't it? :-)

"which is phps default include dir"

I wonder which version of PHP you installed.

By default, PHP's include path is empty, and it would certainly be an extremely bad (and stupid) idea to make it default to the tmp directory (which is world-writable)

One point you do have is that the directories mentioned in the include path must exist or PHP will throw an error. But that has nothing to do with the tmp dir.

About the include paths, indeed we have a difference of opinion. I wouldn't call my solution flawed, more 'based on experience'.