> is that if
> > > there's 2 CFLOGIN tags on the page, the second one always assumes
> > > that your not logged in.
> >
> > You mean 2 blocks of cflogin tags? I'd consider that a bug,
> but also
> > non-standard usage. There should only be one <cflogin> block per
> > request (imho).
> It is non-standard, but something that popped up as I'm testing this.
> Basically, using the CFLOGINUSER inside the CFC causes some
> strange results and that double CFLOGIN issue may be one of
> them. I'm still looking.
> The bottom line may be that its better to leave the
> CFLOGINUSER outside the CFC.
I've always said this. ;) To me, cflogin user is a application specific
implementation. Your CFC should be more vague and simply handle the
authentication. Let the app handle how to remember that the user is logged
in. But we disagreed about this before. :)
Please log a bug about the N uses of <cflogin>. I still say it shouldn't be
used like that, but certainly it needs to work correctly if it can be used
more than once.
> > > Also, the IsUserInRole() function will not take more than
> one role
> > > where the docs says that it can take a list.
> >
> > Yes, it will take more then one role. This works fine in
> all my tests.
> > However, do not forget thatit will do an AND check. So if
> you pass A,B
> > it will only return true if the user is in both.
> Ah, the docs imply an OR case. I've tested it and it is the
> AND case as you say. One of these days I'm going to rewrite
There is a CFLib function that will do an OR check for you. I believe it is
called IsUserInAnyRole.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
