Awkard install still not working...

[Brad Fears]

Actually, the output from that script should NOT have been "'isloggedin' has no value".

It should have assigned a value to the 'isloggedin' session array variable and echo'ed that value.

Now I'm confused too.

--Brad Fears

[Nobody/Anonymous]

Some interesting ouput from the following scripts...

<?php
/* eqeq_ext.php: Equal equal test, extended output */

session_start();

if ($_SESSION['isloggedin'] == "yes") {
echo "IF statement was executed, value: ".$_SESSION['isloggedin'];
} else {
echo "ELSE statement was executed, value: ".$_SESSION['isloggedin'];
}

?>

OUTPUT...
Notice: Undefined index: isloggedin in C:\Inetpub\test\eqeq_ext.php on line 6

Notice: Undefined index: isloggedin in C:\Inetpub\test\eqeq_ext.php on line 9
ELSE statement was executed, value:

================================
<?php
/* neq_ext.php: Not equal test, extended output */

session_start();

if ($_SESSION['isloggedin'] != "yes") {
echo "IF statement was executed, value: ".$_SESSION['isloggedin'];
} else {
echo "ELSE statement was executed, value: ".$_SESSION['isloggedin'];
}

?>

OUTPUT...
Notice: Undefined index: isloggedin in C:\Inetpub\test\neq_ext.php on line 6

Notice: Undefined index: isloggedin in C:\Inetpub\test\neq_ext.php on line 7
IF statement was executed, value:

...I cleared my cache/cookies/temp/etc and I think that might have cleared up some of the quirky problems that were going on.

The logic (above) seems to be working correctly... I am wondering now if this overall issue might be related to the level of error reporting I have specified for PHP.

What level of error reporting do you have your installations set to?  Mine is set to "E_ALL" (all error information is reported).

Tj

[Brad Fears]

My php.ini shows the default:

error_reporting  =  E_ALL & ~E_NOTICE

I still think this is a php bug in windows.  Any chance you have another machine around to try it on?  If not, would it be possible to roll back your php version to something like 4.0.6 for testing?  I'd like to narrow it down to a particular php version.  From what I've read, this problem started popping up after versions 4.1.2 on windows platforms.

Another thing, are you using the stock php.ini?  If not, what changes were made to it?

--Brad Fears

[Nobody/Anonymous]

Hey that solved the prob! I changed my error level to match what you had... and it all looks perfect now!  So it wasnt really an error, it looks like it was warnings that were being spit out.  I believe this was the default warning level when I installed it (I might've changed it as I do some dev/testing stuff on this box too and like to see all errors until I roll something out).

If you are still interested I would be willing to roll back to a previous version, but it appears to be solved (not garbage on the screen/broken functionality).  I logged in and clicked around with out so much as a single error notice.  Also, I refreshed those two snippets I posted earlier (eqeq_ext.php & neq_ext.php) and now they output cleaning the correct text without the error message.

Thanks for sticking with me on this, and I am glad I should now finally be able to use the app :)

Let me know if there is anything else you want me to do, as I am very greatful for your patience with this issue.

Regards,
Tj

[Brad Fears]

Wow.  I wonder if the stock php.ini for Windows has that level of error output...  In any case, I'm glad to hear it's all working now.

Now that you finally have v0.3 working, you'll be glad to know that v0.4 is coming out shortly. :)

--Brad Fears

[Nobody/Anonymous]

doh! :)