ansaurus

Question

What are session.bug_compat_42 and session.bug_compat_warn?

Answer 1

+1 A:

it means your session defines a variable which also exists in global scope. and php thinks you wrote the code in a version < php4.2 and assumes you are actually trying to access an "unset" session variable from global scope.

something like

$_SESSION["foo"] = null;
$foo = "bar";

causes a warning which you can ignore by setting those php.ini parameters to "0"

kali 2010-08-26 13:28:46

Thanks for the reply. But even this doesn't make more sense to me as my register global value is off. So I guess there should not be any conflicts!! Let me know if I am wrong

jtanmay 2010-08-26 14:13:54

there really is no conflict.all thats happenning is php thinks you've written this piece of code before php 4.2 and warns you that functionality is no longer available. it does not(or did not) depend on register globals

kali 2010-08-26 15:04:37

@kali, so you are suggesting that the joomla should be having some depreciated code!?

jtanmay 2010-08-26 17:54:08

no :sjoomla is not written prior to php 4.2$_SESSION["foo"] = null;$foo = "bar";or the opposite of this is probably happening.or most likely$_SESSION["foo"] = $aVariableThatJoomlaNormallyFindsButDoesNotExistInYourSystem;$foo = "bar";is happening in your case.so php just warns you that your version is bigger than 42 and you can not assign "bar" to $_SESSION["foo"] this way. (which ofcourse you've never intended!)

kali 2010-08-27 14:26:41

@Kali, thanks for your reply. My confusion got more complicated yesterday!!! I installed WAMP in my PC(before I was trying at workstation at my office!), and the joomla 1.5.20 installation went smooth even though the above 2 PHP session parameters were ON. I'll try to debug more and let you know if I find any thing. Thanks for your reply again, marking as correct for me :)

jtanmay 2010-08-29 02:30:14

ansaurus

tags:

views:

answers:

What are session.bug_compat_42 and session.bug_compat_warn?

related questions