Hi Jeff, yes I am hoping for the 'lightbulb' effect to kick in real quick! At the moment just as I thiunk I am 'getting it' I manage to confuse myself again. I am presently stuck on getting my head around the Circuit.xml files at the moment. In my fusebox.xml file I have the defaultfuseaction set to login.userdetails, I do not have anything entered into my main circuit.xml file. I have a circuit called login and inside that i have a circuit.xml file with a fuseaction called 'userdetails' that then includes a login page. My idea being that once I have validated the login I will redirect to another circuit called default that will also contain a circuit.xml file that contains a fuseaction called 'homepage' that includes the default homepage file and holds the page output inside a contentvariable (with me so far?) and also a 'do' call that builds the page presentation that then refers to the contentvariable. I think that I am getting tied up on the whole pre/postfuseaction, globalfuseactions, etc bit. Am I heading along the right lines with my thinking here? Are you able to have pre/post fuseactions inside every circuit.xml file if needed? Am I barking up ther wrong tree here? God my head hurts!!!
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tue 15/02/2005 16:03 To: Fusebox Subject: RE: Newbie on Fusebox4.1 Welcome to Fusebox, Andy. Hang in there; there's a point in the FB learning curve that I think of as the "lightbulb" or "eureka" moment. Things seem muddled until the lightbulb goes off, then it's all so clear. It's a funny phenomenon, but every Fuseboxer I've talked to has been through it. For an application like yours, where you don't want a user to see anything unless they log in first, a two-circuit (at least) design is appropriate. The first circuit would be Login (or Security, or Doorman, or whatever you choose to name it, and the other circuit would be whatever the app is--I'll use "Catalog" as an example. The trick is to have a display layout for Login, and a different one for Catalog. You put your "is the user logged in?" detection in Application.cfm or index.cfm, such that if the user is not logged in, your redirect them to something like Login.showLoginForm. If the user is not logged in, they get redirected, and Fusebox uses the layout for the Login circuit (which doesn't have your menus, etc.). Otherwise, they don't get redirected, and Fusebox uses the layout for whichever non-Login circuit they've requested. You can include the circuit's layout display in the postfuseaction element in circuit.xml. That way it only gets executed for fuseactions in that circuit. - Jeff ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:12:6603 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/12 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:12 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.12 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
