Yeah! I think this is the solution, thx man!
-----Mensaje original-----
De: David Huyck [mailto:[EMAIL PROTECTED]]
Enviado el: jueves, 18 de abril de 2002 15:34
Para: [EMAIL PROTECTED]
Asunto: Re: fuse location and fbx_switch question
Try this in your fbx_Settings file:
<cfif not Fusebox.isCustomTag>
<cfmodule template="index.cfm" fuseaction="common.getFestivities"
return="getFestivities">
</cfif>
That way, it only gets called when the fbx_settings is run NOT within a
cfmodule call. Make sense?
David Huyck
[EMAIL PROTECTED]
----- Original Message -----
From: "Xavi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 18, 2002 12:40 AM
Subject: RV: fuse location and fbx_switch question
I was entering in a infinite loop.. Try it.
If I use <cfmodule template="index.cfm"
fuseaction="common.getFestivities" return="getFestivities"> on
fbx_settings root I get an infinite loop
But if I use <cfinclude
template="#fusebox.rootPath#common/qry_getFestivities.cfm"> it works..
If I use cfmodule out the fbx_settings then works.
Why?
-----Mensaje original-----
De: Lee Borkman [mailto:[EMAIL PROTECTED]]
Enviado el: mi�rcoles, 17 de abril de 2002 15:22
Para: [EMAIL PROTECTED]
Asunto: Re: fuse location and fbx_switch question
Why can't you use CFMODULE in fbx_settings? I've never heard that one
before. Just be aware that you mightn't have set the value of #self#
yet. Apart from that, I can't see any problem. Mind you, that doesn't
mean I think of too many good reasons to do it. ;-)
----- Original Message -----
From: Xavi <mailto:[EMAIL PROTECTED]>
But u can't use cfmodule in fbx_seetings root . so, if u want call a
qry_whatever in fbx_settings.cfm u must call it with cfinclude, does
make sense?
-----Mensaje original-----
De: Lee Borkman [mailto:[EMAIL PROTECTED]]
Hi B,
You can use CFMODULE calls within fbx_switch. You do this when you want
to reuse a function that is more involved than a simple atomic fuse.
A common example is adding a serach for to a search results page. You
have already built the "displaysearchform" fuseaction and another call
"displaysearchresults". Now you decide that you'd like to include a
form to do another search on the results page. No sweat - use CFMODULE
within the displaysearchresults fuseaction to invoke the
displaysearchform:
<cfcase value="displaysearchresults">
<cfmodule template="#fusebox.rootpath##self#"
fuseaction="search.displaysearchform" stoplayout="true">
<cfinclude template="qry_searchresults.cfm">
<cfinclude template="dsp_searchresults.cfm">
</cfcase>
So this fuseaction invokes one high-level fuseaction, plus two low-level
fuses to perform its required job.
That means that you now have the search form code in one and only one
place. You can enhance it, optimise it, blah blah blah it, and all the
changes get carried into the sewarch results fuseaction as well.
Now, the meaning of fuseaction="adminrules.ValidateEmail" ...
In FB3, each fuseaction lives within a particular circuit. In order to
call a particular fuseaction, you have to give the name of the circuit
and the name of the fuseaction within that circuit.
So fuseaction="adminrules.ValidateEmail" means "give me the fuseaction
called ValidateEmail within the circuit called adminrules".
Hope that helps,
LeeBB
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
