Re: Re: Your script possibly relies on a session side-effect which existed until PHP 4.2.3
| From: | Justin French | Date: | Wed, 12 Mar 2003 23:35:29 +0000 |
| Subject: | Re: Re: Your script possibly relies on a session side-effect which existed until PHP 4.2.3 | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-139413@lists.php.net to get a copy of this message | ||
My *GUESS* is that you're using:
session_register('var')
session_unregister('var2')
rather than
$_SESSION['var'] = 'something';
unset($_SESSION['var2']);
Either that, or you're referring to session vars as $var instead of
$_SESSION['var']
Give that a go and see what happens.
Justin
on 13/03/03 8:40 AM, Dave Myron (dave@orangechicken.com) wrote:
>> Warning: Unknown(): 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,
>> respectively. in Unknown on line 0
>>
>> register_globals = off
>> (error reporting set to highest possible at runtime)
>>
>
> I'd really like to know the cause of this too. I don't want to set
> bug_compat_42 on... If there's a proper way of coding the PHP then
> that's what I'd rather do, not just make PHP accept my buggy code. What
> is the root cause of this problem?
>
> -Dave
>