Re: [PHP] Re: Your script possibly relies on a session side-effect which existed until PHP 4.2.3

[chris]

On Thu, 13 Mar 2003 10:35:29 +1100, Justin French <[EMAIL PROTECTED]> 
wrote:

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 ([EMAIL PROTECTED]) 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

Justin apparently missed the message Dave replied to (which was mine).  You 
know what happens when you assume Justin?  You make an ass out of you and 
me.  So here's a repost for you:

1.  Registered globals are off.
2.  Using super globals ($_SESSION instead of $HTTP_SESSION_VARS)
3.  Setting via $_SESSION['var'] = $var instead of session_register('var')
4.  Always calling $_SESSION['var'] instead of $var (registered globals are 
off, so it really isn't an option, now is it?)
5.  Unsetting via unset($_SESSION['var']) instead of 
session_unregister('var')

Now, if any other geniouses would like to help me (or any other frustrated 
4.3.1 users) figure out a solution for this vague error message, don't 
follow Justin's very unhelpful footsteps.

Here's another odd tidbit:  I was able to get rid of the message on one 
page by taking out one of the selects in my MS SQL query.  It mattered 
specifically which column it was that I removed from the query and there 
are no other variables throughout the entire project that match the 
column's name.  The warning only pops up on very specific pages, despite 
the consistent coding style throughout the project.

Maybe I'll have better luck posting to bugs.

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php