The locks are another attempt to save myself grief - I didn't think they were necessary either, but I'm at the point were I'm desperately trying anything.


I thought the way the cflogin tagged worked was that it would not execute if the cflogin structure was defined, as that was done automatically on including the j_ tags in the input screen. But I'll try that, and see if it works.

-----Original Message-----
From: Raymond Camden [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 8:13 AM
To: CF-Talk
Subject: RE: cflogin/cflogout

In generla, the login code looks correctly (btw, you really don't need
all those locks) - one question for you - what happens if you do NOT
check for isdefined('cflogin') and instead check form.whatever, whatever
being the form fields you are using (I'm assuming j_username and
j_password). You would also need to change the use of cflogin.name to
form.whatever. In the past, I've seen issues w/ caching of the cflogin
scope, so I stay away from it.

Also, I'd add debug messages. You say your roles don't change, but are
you sure it's not your query returning the wrong results?

  _____  


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to