it's probably easier to just use an absolute path to reference:
set_include_path('/path/to/files');
this way you have a reference point for all your future includes. includes are handled relative to the point they were called, which can cause a bit of confusion in certain scenarios.
as an example, given a sample folder structure (/home/files
):
index.php
test/
test.php
test2/
test2.php
// /home/files/index.php
include('test/test.php');
// /home/files/test/test.php
include('../test2/test2.php');
if you call index.php, it will try to include the following files:
/home/files/test/test.php // expected
/home/test2/test2.php // maybe not expected
which may not be what you expect. calling test.php will call /home/files/test2/test.php
as expected.
the conclusion being, the includes will be relative to the original calling point. to clarify, this affects set_include_path()
if it is relative as well. consider the following (using the same directory structure):
<?php
// location: /home/files/index.php
set_include_path('../'); // our include path is now /home/
include('files/test/test.php'); // try to include /home/files/test/test.php
include('test2/test2.php'); // try to include /home/test2/test2.php
include('../test3.php'); // try to include /test3.php
?>