Jeff, you have just helped me have my first fusebox lightbulb!!! Thank you so much, at least I should get some sleep tonight. Now before my train of thought completely runs away with me, based on the order of process below am i correct in thinking that all application wide variables, such as I used to initialise/setup in aplication.cfm, should now be done in fusebox.init.cfm i.e. DSN settings? Secondly, as users have to login before accessing my site would I simply create a postfuseaction property in my login circuit.xml and set my user specific session variables there? And if I am thinking correctly logic then suggests that I can use a prefuseaction property in circuit.xml for initialising thigs that I need to have access prior to my fuseaction page being loaded, i.e. retrieving data from the database required for the requested fuseaction? Andy McShane Head of Development Scout7 Ltd Acorn House 22 High Street Sutton Coldfield West Midlands B72 1UX Tel: +44 (0) 121 354 7770 Fax: +44 (0) 121 354 4245
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tue 15/02/2005 16:44 To: Fusebox Subject: RE: Newbie on Fusebox4.1 You're right on track, Andy. So far everything you've stated is correct. Let me see if I can help you towards the "lightbulb". The Fusebox process assembles fuses according to a hierarchy consisting of the application configuration file (fusebox.xml) and the circuit configuration file (circuit.xml) for the requested fuseaction. There is only one fusebox.xml per application, while there is a circuit.xml for each circuit. Fusebox puts things together in this order: - Fusebox.xml - preProcess plugin (if any) - preFuseaction plugin (if any) - global preprocess fuseaction (if any) - Handoff to circuit.xml: - prefuseaction (if any) - requested fuseaction - postfuseaction (if any) - global postprocess fuseaction (if any) - postfuseaction plugin (if any) - postprocess plugin (if any) (This is taken from p. 230 of my book, "Fusebox 4 & FLiP: Master- Class ColdFusion Applications".) If the requested fuseaction uses the <do> verb to call other fuseactions as part of its job, those requests are processed in the same way before control returns to the global postprocess fuseaction in fusebox.xml. - Jeff ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:12:6606 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
