You might want to start by flow charting the site (physically speaking).
This will give you a map of what the page flow is.
Eric
-Original Message-
From: Mike Kear [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 7:29 AM
To: CF-Talk
Subject: Fusebox - is there a trick to
On 7/25/07, Mike Kear [EMAIL PROTECTED] wrote:
Is it a simple/trivial thing to convert to fusebox 5+ ?
Well, in *theory* it's just a matter of installing the FB51 core files
under your webroot (or elsewhere and add a /fusebox5 mapping) and then
you just change your application's index.cfm to
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,
I'd say the debugging information with order of execution and execution
times and templates and paths is most useful for this. It tells you what
templates are being executed and where.
-Original Message-
From: Mike Kear [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 8:29 AM
If you have debug access I have an enhanced debug template that shows the full
flow of an application. It includes standard templates, components, custom tags
and includes in a full tree view.
~|
Get involved in the latest
Thanks Michael, that sounds interesting. I'd like to have a look at
that. I'm new to fusebox, and I have to say I'm yet to be convinced
it's better than the way I do my own sites. But i inherited it, and
it's not going to be rebuilt any time soon, so I have to roll my
sleeves up and learn
Michael, is this available somewhere?
I'd really like to check it out.
-Original Message-
From: Michael Dinowitz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 9:13 AM
To: CF-Talk
Subject: Re: Fusebox - is there a trick to following the flow?
If you have debug access I have
On Wednesday 25 Jul 2007, [EMAIL PROTECTED] wrote:
Michael, is this available somewhere?
I'd really like to check it out.
Turn on the relevant debug option in the CF admin.
--
Tom Chiverton
This email is sent for and on behalf of
He said it's a custom template. Like you set in the administrator.
-Original Message-
From: Tom Chiverton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 10:10 AM
To: CF-Talk
Subject: Re: Fusebox - is there a trick to following the flow?
On Wednesday 25 Jul 2007, [EMAIL
It wasn't that steep when I tried learning it, but then again, I learned
on FB3. :)
The idea is that you only open up 1 circuit.xml file at a time. trace
down the error that's causing a fuseaction to go kaput and then move
onto the next.
It shoulds like you are opening all the pages that have
Sandra, thank you!That looks extremely helpful.
What does parameter name=mode value=development / do? Does it
force a reload of the XML files every page view? If so, that's what
i've been looking for for days now!
And yes, this app seems pretty well written by the previous guy. IT
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
Thanks for your suggestion Phillip.
Actually what I am currently tasked with is duplicate part of the
functionality of one circuit in a new circuit. At first sight, all i
have to do is copy that circuit to a new folder, tweak the
circuit.xml.cfm files a bit and change the dsp files to show the
I'd recommend that you call the fuseaction in question, rather than copy the
file itself.
You would do this using the do action=circuit.fuseaction / verb. That
way the core files will take care of making sure your dependencies are all
there, and you will have very little editing to do.
Even if
Development mode forces a reload of the circuit files, parsed files and the
fusebox with each call. Production mode will only reload the parsed files
if they aren't there and it won't pick up changes in the circuit files
either. The problem is that forcing the recall from production mode to pick
Thanks Sean. Your advice is very welcome.
It's a Fusebox 4.0.2 app. The circuits folder has 28,000 files in
it! Took 45 minutes just to unzip onto my dev PC.
Is it a simple/trivial thing to convert to fusebox 5+ ?It's not
going to be something i'm going to be paid to do, so it needs to
I would investigate migrating it to FB5 because the FB debug is awesome. You
can turn the CFdebug off then.
Greg
On 7/25/07, Sandra Clark [EMAIL PROTECTED] wrote:
Development mode forces a reload of the circuit files, parsed files and
the
fusebox with each call. Production mode will only
On 7/25/07, Mike Kear [EMAIL PROTECTED] wrote:
What does parameter name=mode value=development / do? Does it
force a reload of the XML files every page view?
Yup. It'll makes things run slowly (since the framework is reloading
on every request) but it will enable you to test the changes you
18 matches
Mail list logo
