I usually don't bother with FormURL2Attributes.cfm.
I hard code what I want.
Most recently, I've been working on a CF app where I use
<CFINCLUDE TEMPLATE =
"/folder1/folder2/folder3/index.cfm/ds1.ds1value/ds2.ds2value">
where the folder sequence implicitly defines the fuseaction,
and the dsi.dsivalue pairs pass variable names and their
values from one fuseaction to the next. At the time, this
was most most straight-forward way I could see to develop
breadcrumb navigation support.
In addition, the folder's are CF mapped. So none of the *real*
CF templates are in a folder that can be accessed by the web
server, except for the obligatory index.cfm
I might try to abstract it in the future, but I'm not sure.
It works pretty well hard coded.
best, paul
At 05:30 PM 7/25/00 -0400, you wrote:
>Once this is done, I still cannot call pages with index.cfm/ds/main but i
>can still call them with index.cfm?ds=main. Just another note, I have
>renamed "fuseaction" to "ds". Thanks again
------------------------------------------------------------------------------
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.
