Maybe this is where I am misunderstanding the basic concept. I wasn't aware that I needed a copy of each of the 3 files you mention in each folder? I suppose it makes sense though.
So when I am calling the index.cfm file, it will be in the MyApp folder and the fbx_circuits file will direct my fuseaction to the right folder and then direct the request to the fbx_switch file, correct? [EMAIL PROTECTED] wrote: > > What's happening is the information before the dot identifies the > circuit and the information after the dot identifies which fuseaction to > run. > > Here's what's right: > -- Your reference to the fuseaction is perfect. > index.cfm?fuseaction=Rules.myFuseaction > > Here's what you need to double check: > -- Make sure you're fbx_circuits is in the myAPP folder (which could be > named anything, but let's assume you've named it myApp). > > Here's what you need to fix: > -- In the myApp/Administration/Rules folder, you will need the > following files fbx_settings, fbx_layouts, and fbx_switch. The circuit > information in the fuseaction will direct you to this fbx_switch file, > so all you need is the fuseaction. > -- In this switch file you will have the following case statement > <cfcase value="MyFuseaction"> > <!--- includes here ---> > </cfcase> > > Hope that helps. > > > > > > [EMAIL PROTECTED] > > > m To: [EMAIL PROTECTED] > > > cc: > > 04/19/02 11:35 AM Subject: still a bit confused > > > Please respond to > > > fusebox > > > > > > > > > > > Hi All, > > I am still somewhat confused... This example is from bombusbee.com and > is in reference to the fbx_circuits file: > > > ============================================================ > Example > The following is a sample of the code in a fbx_Circuits file: > ?<cfset fusebox.Circuits.Home="myApp"> > ?<cfset fusebox.Circuits.Admin="myApp/Administration"> > ?<cfset fusebox.Circuits.Rules="myApp/Administration/Rules"> > ?<cfset fusebox.Circuits.Front="myApp/FrontEnd"> > > This allows all references to specific folders to be made using aliases. > > To call the Fuseaction named > 'myFuseaction' in the folder myApp/Administration/Rules, you would call > the index.cfm file as > follows: > > index.cfm?fuseaction=Rules.myFuseaction > ============================================================ > > > Now in my fbx_switch file, i would handle this request...how? LIke > this: > > > <cfcase value="RUles.MyFuseaction"> > <!--- includes here ---> > </cfcase> > > > THis is why I am confused: > > This isn't clear to me: "To call the Fuseaction named 'myFuseaction' in > the folder myApp/Administration/Rules..." > > I thought fusactions 'lived' in the fbx_switch file. That is to say, > fuseactions are comprised of various cfm files which handle some > specific task, which is a subset of a larger grouping such as a login > app, or registration app(which would be a circuit). > > Within the fusactions are the atomic elements(files) which when grouped, > > perform a certain task related to the larger app(or circuit). So how is > > it that a fuseaction is in a folder somewhere?? I can see that all the > atomic level files related to the "login" app would be in one circuit, > perhaps name, "Login". But, I dont see how the fuseaction is in the > folder as the bombusbee sample describes. > > ALso, in a complex application, where is the logic in using the aliases > to name circuits? If I see 'Rules.MyFuseaction' in the fbx_switch file, > > that doesn't seem to help me know that that request has to do with some > aspect of administration?? > > > I know I am way off here and I just need someone to turn the light on > for me. Tell me what I am missing :) > > Thanks! > > bidllc > > > ==^================================================================ 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 ==^================================================================
