Edit report at http://bugs.php.net/bug.php?id=54197&edit=1
ID: 54197
Updated by: paj...@php.net
Reported by: julientld at free dot fr
Summary: [PATH=] sections incompatibility with
user_ini.filename set to null
Status: Assigned
Type: Bug
Package: PHP options/info functions
Operating System: Windows Server 2003 SP2
PHP Version: 5.3.5
Assigned To: pajoye
Block user comment: N
Private report: N
New Comment:
@carsten_sttgt at gmx dot de
It is not supposed to be done in a section. But at the global level.
However it
should not crash so please verify that it actually crashes with 5.3.6RC2
(or
not).
The problem here is about the ability to disable the functionality by
not
setting the filename option, as described in the manual.
Now, for any further comments about your specific issue, please open a
new
report. Thanks for your understanding. (ich kann es auch auf Deutsch
schreiben,
wenn es hilft ;)
Previous Comments:
------------------------------------------------------------------------
[2011-03-09 12:27:07] carsten_sttgt at gmx dot de
> For the reason I just mentioned in the same paragraph.
Sorry, which reason? So you mean the different order (at least the
function trace is also the same)? IMHO I'm doing the same as the OP.
BTW: also happens with 5.3.6RC2.
------------------------------------------------------------------------
[2011-03-09 12:22:44] paj...@php.net
For the reason I just mentioned in the same paragraph.
Please open another bug for this problem, thanks.
------------------------------------------------------------------------
[2011-03-09 12:19:30] carsten_sttgt at gmx dot de
> user_ini.filename is not meant to be changed but having one value per
> PHP instance. It should not crash but that's a different issue as the
> one described here.
Why is this a differnt issue?
> [2011-03-08 18:25 UTC] julientld at free dot fr
>
> ;I do not want users to set their own configuration file
> so I disable the below option (set to null)
> user_ini.filename =
>
> [PATH=D:/www/]
>
> I obtain no error if I remove the [PATH=] section or set a filename
to
> user_ini.filename
And that's what I'm doing:
- Having a PATH section (which value must the same as the script which
is executed)
- defining user_ini.filename to nothing
--> result crash
Maybe you mean a different order?
------------------------------------------------------------------------
[2011-03-09 12:01:52] paj...@php.net
Please report only using the 5.3.6RC2 if crashes do not appear with this
version.
@carsten_sttgt at gmx dot de
user_ini.filename is not meant to be changed but having one value per
PHP
instance. It should not crash but that's a different issue as the one
described
here. Please open a new bug using the latest release (5.3.6RC2 if
possible).
------------------------------------------------------------------------
[2011-03-09 11:54:00] julientld at free dot fr
Your problem seems to be a little different from mine, no?
Me, I can't set user_ini.filename to null if I want to use PATH
sections. I do not want to define a user_ini.filename value in a PATH
section. But there are perhaps multiple bugs concerning these features
that said.
------------------------------------------------------------------------
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/bug.php?id=54197
--
Edit this bug report at http://bugs.php.net/bug.php?id=54197&edit=1
