manage, so that they can have a members only area. Simple logon based on
member id - no password or anything that complex (they cannot figure out
how to tell people their passwords at the moment, and it's just a gateway to
keep the general public out). Session var tracks whether the user is logged
in and what the member ID is.
Works fine from a PC
Craps out on a Mac. I've had a couple of Mac users try it, all see the same
problem, which is that after entering their member ID, they get the logon
screen again, which means that the session var with the member id isn't
there. I gave them each a page to use that would dump out all the
url/session/cookie/application/cgi vars, and told them to hit it twice in a
row (so that I could see if the cf tokens stayed the same, so I could see if
cookies were being set). What I see is that cookies are in fact being set,
because for any of the users, all of their info has the same CF token info.
It doesn't look like the session vars are keeping their values. The form
processing page stored the member id and name in 2 session vars, and the
CFLOCATIONs back to the members-only "home page." That page always checks
to see if the user is logged in by checking for a non-zero member ID, and if
the user is not logged in then puts up the logon screen. For some reason
when Mac users do this, the session var values being set on the form
processing page are not there when the home page CF script is processed.
Stumped. Any ideas?
Thanks,
-reed
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
