m3rajk — Thu, 29 Jan 2004 06:07:07 +0000

one of the ones using aol... she uses their browser. i don't know enough about it and said it may be a failure of the browser, and that i know it doesn't understand standards right anyway. the response was that she asked which one i reccommend using. once she started using mozilla it was fine for her.

m3rajk — Tue, 27 Jan 2004 23:33:27 +0000

the irony being that since the last post two that don't use aol went and looked at my quirks section of the faq explaining how to turn on cookies, and viola, it worked. therefore i think it's safe to say now that its either ao-hell for the two iknow are aol users, and browser issues for the rest... i think the one that it didn't work when i changed things recently put on a firewall. i rember her saying something about that, so her firewall might be the isue there. i know zone alarms doesn't allow cookies unless you tell it to (the advanced version) becasue my dad hs it

Mark Hensler — Mon, 26 Jan 2004 05:12:06 +0000

Sounds good.

I still don't see anything wrong with the logic. The only way I find things at that point is by printing every $var I can find to see if any values are not what I expected them to be at that point.

Something else just came to mind... are you doing anything with remote_addr or remote_ip? 'Cause AOL's proxies impare use of those $vars for authentication proceedures. (I don't see the proxies effecting cookies, but who knows - it's a-o-hell)

m3rajk — Mon, 26 Jan 2004 04:19:14 +0000

thanx mark. i wasn't sure how to go about debugging ti. but i found it interesting that one of those with issues earlier didn't have themtonight. makes me feel that there is something on the user side. that and the fact the more i have try it, the more that have it work. it's looking more and more like user side and not client side. i'm going to wait on the added debug until i've had a chance to make sure every one of them has double checked that cookies are allowed by their browser.

you are the first response i got. =o)
so far the only one. so the only reason i'm not doing the debug now is laziness

Mark Hensler — Fri, 23 Jan 2004 07:45:34 +0000

I don't see anything wrong...

You may want to try something like this:

<?php
}elseif($action=='update'){ # updates cookies (keeping you logged in) & returns waiting messages (optional)
$dbug = 'a';
    if(isset($_COOKIE['login'])&&($_COOKIE['login'])){ # we're logged in
$dbug .= 'b';
      $ims=array(); # empty array for any ims we might find unread
      $db=mysql_connect($host, $login2, $pass2) or die(\"cannot access mysql\"); # get the sql connection
      $fyd=mysql_select_db($dbname, $db) or die(\"cannot connect to db\"); # select the db
      $un=$_COOKIE['un']; $pw=$_COOKIE['pw']; # what we wont change on-the-fly
      $fprefs=mysql_query(\"SELECT uid, gmt_offset, tds, login_duration, msgs FROM users WHERE username='$un' AND password='$pw'\", $db); # get the prefs
      if(mysql_num_rows($fprefs)>0){ # we can update the cookies
$dbug .= 'c';
    $prefs=mysql_fetch_array($fprefs); $gmto=$prefs['gmt_offset']; $utds=$tdc[$prefs['tds']];
    $duration=$durr[$prefs['login_duration']]; $accepts=($prefs['msgs']*1); $uid=$prefs['uid'];
    $expire=(time()+($duration*60));
    setcookie('un', $un, $expire); # set username
    setcookie('pw', $pw, $expire); # set password
    setcookie('login', 1, $expire); # set login
    setcookie('gmto', $gmto, $expire); # set the gmt offset
    setcookie('utds', $utds, $expire); # set the time display style
echo \"\n\n<!-- DBUG - DBUG - DBUG - DBUG - DBUG\n\n\";
echo \"dbug=$dbug\n\";
echo \"prefs=\"; print_r();
echo \"duration=$duration\n\";
echo \"time=\".time().\"\n\";
echo \"expire=$expire\n\";
echo \"un=$un\n\";
echo \"pw=$pw\n\";
echo \"login=$login\n\";
echo \"gmto=$gmto\n\";
echo \"utds=$utds\n\";
echo \"\n\nDBUG - DBUG - DBUG - DBUG - DBUG -->\n\n\";
?>

This should give you a picture of what's going on.

The "abc" should probably go right before the return statement. It's purpose is to indicate if any of the conditionals are failing.

Yes, I know how to spell debug. I just felt like saving time by ommiting all the e's.