The root fbx_Settings.cfm file is an anomaly in that it gets executed
before the core file starts it's downward parse through the circuit
hierarchy.

<rant>
IMHO, the root fbx_Settings.cfm shouldn't be fbx_Settings.cfm at all,
because it behaves totally differently from any other fbx_Settings.cfm
file.  There should be two files in the root directory, fbx_Settings.cfm
that gets called as the start of the downward parse, and a new file
called fbx_AppStartup.cfm or something that gets called before the parse
starts.  The former would be circuit specific, and the latter would be
app specific, including things like CFPARAMing attributes.fuseaction and
stuff.
</rant>

But, to answer your question, if you need to have the API variables set
and access them in your root circuit, you pretty much have to put the
code in the fbx_Switch file, or an include thereof.  My choice has
typically been to include app_locals.cfm from my fbx_Switch.cfm as a
throwback to the XFB days.  In your case, you could just use
'#listFirst(attributes.fuseaction, ".")#' instead of
'#fusebox.targetcircuit#', and leave it in fbx_Settings.cfm, but if
you're having to manually generate what the API variables do for you,
then there's a flaw in the framework structure.

hope that helps / my $0.02
barneyb


-----Original Message-----
From: Tom Schreck [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 7:38 AM
To: [EMAIL PROTECTED]
Subject: fusebox.TargetCircuit


When does the fusebox.TargetCircuit variable get set?  I tried using it
in my root FBX_Settings file but it comes back as blank.  I wanted to use
it in the capacity of checking to see if the user is in the
Authentication circuit:

Snippet from fbx_Settings file:
            <!--- redirects user to Authentication circuit --->
            <cflock timeout="60" throwontimeout="No" type="READONLY"
scope="SESSION">
                        <cfif ((Not IsDefined("session.ynLoggedIn")) AND
(fusebox.TargetCircuit NEQ Authentication))>
                                    <cflocation
url="#request.self#?fuseaction= Authentication.login" addtoken="No">
                                    <cfabort>
                        </cfif>
            </cflock>

I may want to include other fuseaction calls in the login page prior to
the user being authenticated.  If I call these other fuseactions via
cfmodule back through index page then the trap above sends users to login
page.  I want to be able to pull in marketing information to show up on
the login page.  The marketing information is stored in a separate
circuit all together.

Thanks -

Tom Schreck
817-252-4900
[EMAIL PROTECTED]

I have not failed.  I've found 10,000 ways that won't work.

- Thomas Edison

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.371 / Virus Database: 206 - Release Date: 6/13/2002

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to