#14401 [Opn->Fbk]: Wrong include_path from Apache <Directory> config

From: Date: Mon, 25 Nov 2002 05:15:36 +0000
Subject: #14401 [Opn->Fbk]: Wrong include_path from Apache <Directory> config
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-25756@lists.php.net to get a copy of this message
ID: 14401 Updated by: iliaa@php.net Reported By: vogel@folz.de -Status: Open +Status: Feedback Bug Type: Apache related Operating System: Linux i386 PHP Version: 4.3.0-dev New Comment: Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip The previously mentioned bug, #18568 has been fixed. Previous Comments: ------------------------------------------------------------------------ [2002-11-11 13:10:10] vogel@folz.de Well, as reported earlier, I need a working RPM installation, which means that bug #18568 has to be fixed, too, which it's not, as of snapshot 200211101739. ------------------------------------------------------------------------ [2002-11-10 18:27:53] sniper@php.net 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. ------------------------------------------------------------------------ [2002-10-27 22:35:01] iliaa@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-09-23 11:52:30] vogel@folz.de Well, I had hoped that the bug fix for the Apache XbitHack would also fix our auto_prepend_file+include_path problem, but it certainly does not. In other words: 4.2.3 has _still_ this problem of wrong include_path's for files loaded via auto_prepend_file. ------------------------------------------------------------------------ [2002-07-23 12:31:42] vogel@folz.de A short note to confirm the obvious: release 4.2.2 did _not_ fix this problem. It took about 24 hours after the upgrade until it happened for the first time. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14401 -- Edit this bug report at http://bugs.php.net/?id=14401&edit=1

« previous php.bugs (#25756) next »