Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.


I could not reproduce the problem.

I found the same problem.
If you use a require_once with a relative path and then you use a require_once with absolute path but to the same file, php include the file twice. I try this bug in version 5.2.x and the problem there isn't.

I'm unable to reproduce this.

tried:
- 2 require_once: 1 relative, 1 absolute
- 2 require_once: 1 relative, 1 absolute with a symlink-dir somewhere in there.

Also, when including/requiring a file with a path that contains a symlink 
somewhere, PHP will resolve the symlink and use the actual path of the location 
(like using realpath).
You can see this when you use the function get_included_files.

I would love to see some code that actually reproduces this. Please post the 
code/files.

I see this problem also.

Assume the following files:
/mylib/css.php
/mylib/needs/supportfile.php

and the contents of css.php are something like as follows:
<?php
require_once('needs/supportfile.php');

class css {
 static function get() {
   return "#col { color: red; }";
 }
}
?>

Then assume an application that uses the css.php library
cd /anApplication
ln -s /mylib css

then create the file /anApplication/test.php with the following contents
<?php
include_once('css/css.php');

print css::get();
?>

This fails as the require_once in css.php does not find the needs/supportfile.php file

Hello again,

my apologies - my comment above is WRONG

The reason for the problem is that I am using samba so what I did in my situation was

1. download a zip file of  the library I am testing in windows
2. extract the zip file over the samba folder
3. referenced the extracted files directly from the linux server presenting the samba folder

To remove the problem I downloaded the equivalent tar version to the linux server and extracted it on the linux server directly - then the require_once worked 100%

So although I cannot prove it - as no error was thrown, the require_once simply didn't work - it appears that the problem was to do with dos/linux file differences. Regardless, though I hope this is useful to someone as it was a nasty problem to track down due to the lack of errors.

apologies for the red herring

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.