#19287 [Ver->Fbk]: updating from 4.2.2 to 4.2.3 file_exists fails
| From: | sander@php.net | Date: | Sun, 08 Sep 2002 14:38:54 +0000 |
| Subject: | #19287 [Ver->Fbk]: updating from 4.2.2 to 4.2.3 file_exists fails | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-18664@lists.php.net to get a copy of this message | ||
ID: 19287
Updated by: sander@php.net
Reported By: soletan@toxa.de
-Status: Verified
+Status: Feedback
Bug Type: Apache2 related
Operating System: Linux 2.4.18
PHP Version: 4.2.3
New Comment:
I expect it to take couple of months... there were many changes to many
core parts of PHP and we haven't even started the QA process...
Can you try the latest CVS (or a non-STABLE snapshot from
http://snaps.php.net/) to make sure it has been fixed?
Previous Comments:
------------------------------------------------------------------------
[2002-09-08 09:22:39] soletan@toxa.de
okay, it's Apache2 SAPI here, too. When will 4.3.0 be published
finally? I can't use dev-versions on a production web site ...
------------------------------------------------------------------------
[2002-09-08 02:54:22] sander@php.net
Can't reproduce with 4.3.0-dev.
------------------------------------------------------------------------
[2002-09-07 16:51:44] edink@php.net
I can reproduce the problem, but only using Apache2 SAPI. It seems that
file_exists() does not work with relative paths. Using absolute path
seems to be working fine.
------------------------------------------------------------------------
[2002-09-07 16:18:06] soletan@toxa.de
Hi,
PHP runs with Apache 2.0.40 as DSO and there are a few modules selected
to be built into PHP-module. Everything was fine before updating PHP
and I used the same configure-arguments to compile 4.2.3 as before
4.2.2 ...
Well, here comes the problem itself: I've updated from 4.2.2 to 4.2.3
right before and without further changes file_exists returns false in
cases, where it returned true before. Files are existing and logfiles
aren't showing anything. I originally used @ to suppress error messages
and removed it temporarily to get some error message. display_errors is
turned on, too.
But there's no message, while the tested files are world-readable. Now
I change the source to get it back working ... how uncomfortable ... :(
Thanx for your fixing,
Thomas Urban
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=19287&edit=1