ID: 22769
Updated by: [EMAIL PROTECTED]
Reported By: jcobb at reports dot net
-Status: Open
+Status: Bogus
Bug Type: Session related
Operating System: win 2k
PHP Version: 4.3.1
New Comment:
Yes, just don't do that.
Previous Comments:
------------------------------------------------------------------------
[2003-03-18 10:57:36] jcobb at reports dot net
tracking down the problem with the warning message:
Your script possibly relies on a session side-effect which existed
until PHP 4.2.3. Please be advised that the session extension does not
consider global variables as a source of data, unless register_globals
is enabled. You can disable this functionality and this warning by
setting session.bug_compat_42 or session.bug_compat_warn to off,
i've found another strange observation: people are reporting problems
with their settings in php.ini, e.g. setting bug_compat_warn=off will
not make the message go away.
the message WILL indeed disappear, but only if the server is freshly
restarted and no session file is present. given example:
php.ini:
session.bug_compat_42 = 1
session.bug_compat_warn = Off
code used:
session_start();
if (! session_is_registered("foobar")) { print "registering";
session_register("foobar"); $foobar=1; }
clear all session files; restart server; reload > no warning.
then: remove the session file that was just created;
reload > warning reappears and will remain no matter
what you do.
how does this make sense? there should be no difference between the
first call and the second. if the session file is missing, it's missing
and a new one should be generated.
i've reproduced this on 3 different systems and could not believe it.
can you check if there is a flag that messes things up after displaying
the message for the first time?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=22769&edit=1
