Hi David,
The method I use for defining default fuseactions (and I believe Hal might
be heading in a similar direction?) is to invoke the default action like
this:
index.cfm?fuseaction=circuitXYZ.default
Within each circuit, you make sure that there is always a fuseaction named
"default", but this is usually "doubled up" with an existing fuseaction.
For example, is the default action for the circuit "phone" should be
"searchform", then you CFSWITCH has this kind of code in it:
<CFCASE VALUE="searchform,default">
<CFSET...
<CFINCLUDE...
<CFINCLUDE...
</CFCASE>
In other words, you can just add the "default" label to any fuseaction you
want. Then everyone else can just assume they can call "phone.default" and
something sensible will happen.
[I suspect, however, that the 404 error is more to do with server config, eg
whether or not you have a default file (eg index.htm or index.cfm) for
directory browsing.]
LeeBB
>From: "David Vause" <[EMAIL PROTECTED]>
>
>I did notice a difference between the two that I'm not
>so crazy about. Say I have my main fusebox and a circuit
>located in a child directory called "users." What I liked
>about standard fusebox was the use of simple URLs. For
>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.)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
