There was once a time when I thought I had a handle on this web application
development thing.... sometimes I do have to wonder though, when seemingly
simple things defy my understanding. I hope that someone is willing to help
me understand this bit of trivia.
I've always used relative paths to my cf templates .. hell.. before fusebox,
my directory structures were nearly irrelevant - but now, well into the
bardo of fusebox, the whole structure becomes clouded - this traveler
becomes confused as to what hunk of code is actually in control at any given
moment, which makes knowing where my files are all the more difficult.
I'm writing my first application with nested fusebox circuits and although I
feel I have the basic flow of the thing down, I am repeatedly hitting on
"Missing Include"'s and references to missing this' and that's that seem
like they are where they should be.
Can someone please tell me:
1.) What paths to virtual directories do I need in my web server?
2.) what mappings do I need to find my cfincludes?
3.) what variables should I be defining (and redefining at sub-circuit
levels) so that I can find "myself" and my place in the directory universe?
can code from one circuit easily access code from a "higher or lower"
circuit plane of existence?
I'm obviously trying to avoid the dreaded "../" and hellishly long path
names tied to my image src's, links and form actions... is there some simple
primer I may discover that lets me see the light and achieve a meaningful
and lasting hierarchical nirvana?
please, kind guru's - enlighten me.
pts
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
