>
> example, if I want to go straight to the default fuseaction
> in the "users" circuit, I could type
> http://www.someurl.com/users/ directly into my browser and
> go to the default fuseaction for that circuit. XFB
> apparently won't allow for this. (it usually will throw
> a 404 error.)
false :)
you can as easily have the sub-circuit work independently. (in fact, once
you get over this relatively small learning curve hump, you're gonna say to
yourself, "ugh! the OLD way of running sub-circuits sure was ugly!") You can
also have it work in tandem with the root level fusebox. And you can have it
do both. And they're all easy :) You just gotta get it right once and then
the light will click on, so stick with it cuz you're close.
since you're getting a 404 error, i wonder if you might have a small bug in
the Circuits.cfm ? perhaps the sub-circuit is attempting to find a
"myglobals.cfm" and/or its own "circuits.cfm" or etc that isn't there (yet)?
Post it and someone will spy the error fast.
a general rule is that if you want a sub-circuit to work only as a
sub-circuit, then all you need in the sub-circuit is the index.cfm fusebox.
Nuttin else. If you want it to act independently then you'll need to same
files that any "top level" XFB fusebox needs, a myGlobals.cfm and a
Circuits.cfm, etc
there is one thing you give up this way: if the sub-circuit is dependent on
the main fusebox then going to it independently will not work unless you
also add in soem code to make it work independently. (In XFB sub-circuits
get to inherit the properties of the master circuit regardless of depth, but
in standard FB the inheritance only spans the app_globals.cfm and this by
specifically hard-wiring where that key file is.... remember the old
<cfinlcude template="../../../../app_globals.cfm" > :)
But think about this a second...do you REALLY want a user to be able to go
to a section of your code and by-pass anything "higher-up" that you've
specifically intended to be there? if so, then maybe it isn't dependent at
all, in which case the "old" FB way of stitching it together is just a way
of tying together independent FB's. This is not a bad thing -- you've got
complete control over whether you want the user to access the sub-circuit by
itself, or only with the master or both; all you have to decide is which of
the three options you'd like :)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
