php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #16852 Apache2 not compatible with php_admin_value, php_value, php_flag ....
Submitted: 2002-04-26 09:04 UTC Modified: 2002-05-17 07:55 UTC
From: tech at kalyweb dot com Assigned:
Status: Closed Package: Apache2 related
PHP Version: 4.0CVS-2002-04-26 OS: Any
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: tech at kalyweb dot com
New email:
PHP Version: OS:

 

 [2002-04-26 09:04 UTC] tech at kalyweb dot com 
I'm running Apache 2.0.35 / PHP 4.2.0 under win32 (php as a module of Apache) and I can use php_admin,value, etc...

I'm also running Apache 2.0.35 / PHP4.3.0-dev (Auto-updated at Midnight GMT+0200) and here too I can't use php_admin_value etc...

I have friends with also PHP4.2.0 and Apache2 and they can't use php_admin_value .

It seems to be a bug or something that isn't already done in the Apache2 module of php.

Apache2's answer is :
php_admin_value not allowed here.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-04-26 09:13 UTC] derick@php.net 
This was submited some more times already... duplicate.

Derick
 [2002-05-17 07:55 UTC] sniper@php.net 
This bug has been fixed in CVS. You can grab a snapshot of the
CVS version at http://snaps.php.net/. In case this was a documentation 
problem, the fix will show up soon at http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites.
Thank you for the report, and for helping us make PHP better.
 [2002-06-16 08:47 UTC] om at mascia dot biz 
Running Apache 2.0.36 and PHP 4.2.1 on Win32 (php4apache2.dll), I also see this same bug. Said to be fixed in CVS, indeed. But it did not make it in 4.2.1. Is it reasonable to expect a 4.2.2 or the-like fixing or shall we have to wait for 4.3 ? If the answer is "please, wait", could someone send me the diff of that fix so I can fix it in the 4.2.1 code on my own system (to have a workaround) ?
Thank you so much !
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 13:01:31 2024 UTC