PHP 5 function redeclared error

[saayan]

Hi,
I am using PHP 5.0.1 with Apache 2 on Win XP (SP2).

My index.php file has require_once contents.php and also for
functions.php.
My contents.php file also has a require_once for functions.php.

When this code is tested on one machine, it works fine. However on
another machine with identical configuration (same PHP 5.0.1, XP+SP2,
Apache 2), an error message appears :
test_timeout function redeclared.
(test_timeout function is in functions.php file.)

We have tested it with PHP 5.0.3 - same problem happens.

For running the PHP, MySQL, Apache combination, our setup steps are:
1. Install PHP - customize the .ini file
2. Install MySQL
3. Install Apache - customize the httpd.conf for using PHP
4. Copy libmysql.dll from ...\php\ dir to windows\system3 2 dir

The configurations are exactly same for both machines. The two machines
have identical PHP, MySQL and Apache physical directory paths. The
php.ini and httpd.conf (for apache) are copied from machine 1 to
machine 2. And we are testing the code locally using localhost.

Can anyone please give some hint as to the possible cause of this
problem. Am I missing something here?

Thanks,
Saayan

The file locations

home/index.php
home/secure/contents.php
home/secure/functions.php

in index.php:
// blah blah
require_once("s ecure/contents.php");
// blah blah
require_once("s ecure/functions.php") ;

in contents.php:
// blah blah
require_once("f unctions.php");
// blah blah

[Michael Fesser]

.oO(se****@gmai l.com)

There is nothing wrong with PHP w.r.t require_once. The problem is, inmachine 2:

.../home -> has a functions.php
.../home/secure/ -> also has a functions.php

this proves that the require_once('f unctions.php') in contents.php is
failing on server 1...

No!
there is no functions.php in the 'home'
directory (which is where PHP is looking for the file).

PHP looks there first, if it can't find one it looks in /home/secure
(the same directory where contents.php is stored). It's all correct.

Micha

[sesser]

My bad. I was unaware that it would look in the 'secure' directory if
it failed in the 'home' directory. Not to mention that 'require()'
would produce a fatal error if it couldn't find a file.

thanks
r.

[chernyshevsky]

I was trying to simplify things a bit. Unless you change it with a call
to chdir(), the cwd is the same as the script directory. Including a
file in a different directory does not change the cwd to that
directory.

I'm at a loss as to why require_once("f unctions.php") manages to find
secure/functions.php. I think most of us would agree that it's not
supposed to happen, unless /home/secure is in the include_path. If it
is, then why does require_once() fail to see that it's the same file?
Since this happens on Windows, maybe it's a forward slash vs. backward
slash misinterpretati on within PHP.

In any event, providing absolute paths to include/require is the
preferred practice. That way you know for certain what you're
including. An example:

define('SECURE_ INCLUDE_ROOT', dirname(__FILE_ _) . "/secure/");

function require_secure( $filename) {
require_once(SE CURE_INCLUDE_RO OT . $filename);
}

[Andy Hassall]

On 12 Jan 2005 12:59:47 -0800, "ch***********@ hotmail.com"
<ch***********@ hotmail.com> wrote:

I was trying to simplify things a bit. Unless you change it with a call
to chdir(), the cwd is the same as the script directory. Including a
file in a different directory does not change the cwd to that
directory.

Yes, that's the point from the manual snippet I posted. cwd is searched first,
then the directory containing the current script. When you include a script
outside the cwd, then all include_path directories relative the directory
containing the included script become candidates for searching, once all
equivalents relative to cwd fail.

--
Andy Hassall / <an**@andyh.co. uk> / <http://www.andyh.co.uk >
<http://www.andyhsoftwa re.co.uk/space> Space: disk usage analysis tool

[Chung Leong]

"Andy Hassall" <an**@andyh.co. uk> wrote in message
news:fa******** *************** *********@4ax.c om...

On 12 Jan 2005 12:59:47 -0800, "ch***********@ hotmail.com"
<ch***********@ hotmail.com> wrote:

I was trying to simplify things a bit. Unless you change it with a call
to chdir(), the cwd is the same as the script directory. Including a
file in a different directory does not change the cwd to that
directory.
Yes, that's the point from the manual snippet I posted. cwd is searched

first, then the directory containing the current script. When you include a script outside the cwd, then all include_path directories relative the directory
containing the included script become candidates for searching, once all
equivalents relative to cwd fail.

--
Andy Hassall / <an**@andyh.co. uk> / <http://www.andyh.co.uk >
<http://www.andyhsoftwa re.co.uk/space> Space: disk usage analysis tool

Crap. I got egg on my face. I've always understood "current script" as being
the file reported by PHP_SELF. Turned out I'm way off. Thank you, Andy and
Michael, for point it out.