I guess I am a bit confused. Based on the training I did with Hal in February, it was my understanding that proper fusebox methodology would be to call our fuseactions in our switch files in the following way:
<Cfswitch expression="#fusebox.fuseaction#"> <cfcase value="fa"> <cfset XFA.blahbetyblahblah = "child.getOut"> <cfinclude template="dsp_showChild.cfm"> </cfcase> </cfswitch> And in the dsp_ file you would include: <a href="#fusebox.rootpath##self#?fuseaction=#XFA.blahbetyblahblah#">Get out of here!</a> But, I'm finding that this doesn't work for circuits below the root directory. Am I still missing the point? Bradley S. Dardaganian Lead Application Developer MediTech Media Ltd (USA) [EMAIL PROTECTED] (404) 591-3247 -----Original Message----- From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 3:35 PM To: [EMAIL PROTECTED] Subject: Re: #fusebox.rootpath##self# Brad, you should have to be doing things that way (not with FB3). Once you define all your circuits in the root circuit of your app, which seems to be in ABCDEF, then all request will go through the index.cfm in that circuit. The circuits defintions will know what to do and where to go to get the fuseaction "X" in circuit "Y" #fusebox.rootpath# is useful for things are that done *AFTER* the ColdFusion service is done parsing the file -- for example in creating a reference to an <IMG> or similar, something that the web server (not the CF server) will have to respond to once the end-user's browser parses the HTML file. Also, #fusebox.rootpath# is useful in knowing how to get back to your root circuit from any circuit that you might be currently executing some code in -- it's kind like a rope that follows the execution along so that at any time you can easily just follow the rope back to get home. Another useful use of #fusebox.rootpath# is if you are calling one of your sub-circuits *as an independent circuit* -- this should not be happening often if you are just starting out in FB -- and it will also be used when you want to recursively call a fuseaction, such as in using CFMODULE. Again, that's a intermediate-level concept so I'd leave it aside for now until you feel you've got a real handle down on core Fusebox. (hehehe, that should take all of a few days, max!) ----- Original Message ----- From: "Brad Dardaganian" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 3:18 PM Subject: #fusebox.rootpath##self# > Hello Fuseboxers... > > I'm having some issues using the fusebox variables #fusebox.rootpath# > and #self# together. I'm sure it's an easy fix I'm overlooking. > > I'm working on a development server, which we'll call > www.devserver.com, and we'll call my project ABCDEF; so the rootpath > should be: www.devserver.com/ABCDEF. > > If I'm calling a fuseaction below the root directory, however, I have > to do this: > > #fusebox.rootpath#ABCDEF/#self#?fuseaction=circuit.fa > > When I try to call a module using a call like: > <cfmodule template = "#fusebox.rootpath#ABCDEF/#self#" > fuseaction="circuit.fa"> I get a "Template file not found" error. > > What do I need to do to set up my overall project so I can access all > circuits via: #fusebox.rootpath##self# ?? > > Thanks! > > > > Bradley S. Dardaganian > Lead Application Developer > MediTech Media Ltd (USA) > [EMAIL PROTECTED] > (404) 591-3247 > > ==^================================================================ 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 ==^================================================================
