What happens if you remove the cfabort? It may be scewing up the
cfloginuser tag. Also, I _believe_ getAuthUser() will be blank until
you actually leave the cflogin block. I seem to remember that bug.

-ray

On Fri, 06 Aug 2004 11:04:12 -0400, Gel . <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> here's a bit of code I'm using to login users using the CFLOGINUSER TAG.
>
> The output I am seeing is CFLOGINUSER SHOULD BE EXECUTED.
> But I'm not seeing the GetAuthUser(), and the user is never actually logged in.
>
> WHen I type this :
>
>  <CFLOGINUSER NAME="MyName" PASSWORD="MyPassword" ROLES="Admin">
>
> directly into the application.cfm file though it works fine.
> Any ideas as to what I am doing wrong??
>
> act_login.cfm code:
>
> <CFLOGIN>
>         <CFIF NOT (ISDefined("form.username") AND IsDefined("form.password"))>
>                 <CFINCLUDE TEMPLATE="viw_login.cfm">
>                 <CFABORT>
>         <CFELSE>
>                 <CFQUERY NAME="GetUser" DATASOURCE="#request.datasource#" USERNAME="caddo" PASSWORD="caddoxl">
>                         Select userid,username,password,roles from tblusers
>                         where username = '#form.username#'
>                         AND password = '#form.password#'
>                 </CFQUERY>
>                 <CFIF getuser.recordcount EQ 1>
>                         CFLOGINUSER SHOULD BE EXECUTED.
>                         <CFLOGINUSER NAME="MyName" PASSWORD="MyPassword" ROLES="Admin">
>                         <!--- <CFLOGINUSER NAME="#getuser.userid#,#getuser.username#" PASSWORD="#form.password#" ROLES="#getuser.roles#">--->
>                         <CFSET temp=#GetAuthUser()#>
>                         <CFOUTPUT>#temp#</CFOUTPUT>
>                         <!--- <CFLOCATION URL=""> >                         <CFABORT>
>                 <CFELSE>
>
> <!---<CFLOCATION URL=""> >                         <CFABORT>
>                 </CFIF>
>         </CFIF>
> </CFLOGIN>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to