This may help. . . I still use the application.cfm file because it
fires no matter what when CF goes into a directory. And in the file I
place the following code that allows non logged in users to perform
functions that do not require logging in.
<cfif not SESSION.LoggedIn>
<cfswitch expression = "#attributes.fuseaction#">
<cfcase value="stu.dailyimm"><!--- Daily Batch File to update
student immunization. ---></cfcase>
<cfcase value="members.login"><!--- let them login ---></cfcase>
<cfcase value="members.authenticate"><!--- authenticate the login
---></cfcase>
<cfcase value="members.EmailMyPassword"><!--- display a page that
Emails the user their password ---></cfcase>
<cfcase value="members.sendemail"><!--- Email the user their
password ---></cfcase>
<cfcase value="members.newuser"><!--- New User signup ---></cfcase>
<cfcase value="members.saveuser"><!--- New User signup ---></cfcase>
<cfcase value="members.confirm"><!--- New User confirmation
---></cfcase>
<!--- Evaluations --->
<cfcase value="eval.evaluationmessage"></cfcase>
<cfcase value="eval.getcourseevaluation"></cfcase>
<cfcase value="eval.addcourseevaluation"></cfcase>
<cfcase value="eval.getinstructorevaluation"></cfcase>
<cfcase value="eval.addinstructorevaluation"></cfcase>
<cfdefaultcase>
<cflocation
url="#request.wwwroot##self#?fuseaction=members.login" addtoken="No">
</cfdefaultcase>
</cfswitch>
</cfif>
Bob Silverberg wrote:
> I place all of my fuseactions that can be executed by a non logged in user
> in a single circuit app, called "public". I also have a "shared" file
> directory. This "shared" directory includes code that will prevent any of
> the templates from being called directly from this directory. So I place
> all of my fuseactions that anonymous users can execute (e.g., login,
> register) in "public", and I place any files that must be included in both
> public and non-public pages in the "shared" directory.
>
> This works well for me,
> Bob
>
> -----Original Message-----
> From: Mike Craig [mailto:[EMAIL PROTECTED]]
> Sent: March 20, 2001 6:27 AM
> To: Fusebox
> Subject: XFB Login Conundrum
>
>
> I have been using Hal's latest on XFB and have an interesting conundrum. I
> have figured out one or two ways around this but none of them look very
> good. Here is the problem:
>
> From the root, I use two circuits, one for login and one for profiles. The
> profile circuit is actually a control center that requires the user be
> logged in, so the index.cfm file requires it.
>
> So, if you try to go to the control center, you first jump to the login
> circuit then come back to the control center. However, you can start to see
> the catch 22. If I ask to go to the control center and create a profile
> (where all that code should reside) I will first go to the login
> circuit...but I am trying to create a profile, not login.
>
> Of course my one solution is to share the profile code at a higher circuit
> level and share it or another to copy the profile content files into the
> login circuit and the control center circuit.
>
> Is that enough to generate an idea or two?
>
> Mike Craig
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
