Couple of things that will help in Debugging a Fusebox 4+ app. 1) Validate the XML in circuit.xml.cfm. Fusebox will burp on bad XML.
If an error shows up in the parsed file. (circuit.fuseaction.cfm) then the error is in the circuit. Most well done FB4+ apps usually use MVC. The controller will act as your traffic cop. Noting which parsed file is throwing the error, will enable you to quickly move to the controller circuit and fuseaction. In fusebox.xml.cfm make sure that in the <parameters> section that <parameter name="debug" value="true" />. This will turn on some debugging in your parsed files so that you can go down to where the error is and find out which circuit file and lines are throwing the actual error. Make sure to turn this off once you go into production. Always develop in <parameter name="mode" value="development " /> (for Fusebox 4) and <parameter name="mode" value="development-full-load" /> (for Fusebox 5+) Once you go into production <parameter name="mode" value="production" /> if you need to change something in your circuits, delete all parsed files, and call your page with http://yourwebsite/index.cfm?fusebox.load=true&fusebox.password= (you set your password in the parameters section of fusebox.xml.cfm using <parameter name="password" value=""/>. Sandra Clark ============= http://www.shayna.com Training and Consulting in CSS and Accessibility Team Fusebox -----Original Message----- From: Mike Kear [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 25, 2007 8:29 AM To: CF-Talk Subject: Fusebox - is there a trick to following the flow? I have inherited a fusebox4.0 app to maintain that has dozens of circuits that are reused all over the place. I know that's how fusebox is supposed to work, and it makes sense to reuse the fuses, but wow it takes AGES to follow the flow of the program. And i end up with dozens of files open, all called circuit.xml.cfm so its easy to make a mistake following it all along. For example I have to figure out how something works, so i can maintain it, or build something else similar. In order to find out how the task works, i follow one xml file through, seeing dozens of fuses, all of which i have to go to, open the circuits.xml.cfm relating to it, follow that one along, then open more. By the time i've got to the final, actual coldfusoin type tags relating to the functionality, i've almost forgotten what it was i started out to do. Is there a shortcut to working out how everything's bolted together? If i keep taking hours to work out the simplest things i'm not going to last long on this assignment. -- Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Check out the new features and enhancements in the latest product release - download the "What's New PDF" now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:284547 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
