|
Hi B,
No the circuit aliases have no impact on your CFINCLUDE or
CFMODULE locations. These must still reference relative or mapped
locations. In your example, you would probably do this:
<cfinclude
template="#fusebox.rootpath#Administration/Rules/actValidateEmail.cfm">
The circuit aliases are only used in the double-barrelled "circuit.fuseaction". In other words, the circuit alias is part of the description of a particular high-level function of a Fusebox application. As an alternative to reusing the low-level
actValidateEmail.cfm fuse, you could expose the email validation as a
high-level, public fuseACTION. If you did that, then you could reuse that
function via CFMODULE: So you have a few options. Hope that help, Best of luck ----- Original Message -----
==^================================================================ 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 ==^================================================================ |
- fuse location and fbx_switch question bidllc
- RE: fuse location and fbx_switch question Lee Borkman
- RE: fuse location and fbx_switch question bidllc
- Re: fuse location and fbx_switch question Lee Borkman
- Re: fuse location and fbx_switch questi... Lee Borkman
- RE: fuse location and fbx_switch question John Beynon
- RE: fuse location and fbx_switch question Mary-Catherine Gerrey
- RE: fuse location and fbx_switch question bidllc
- Re: fuse location and fbx_switch question Lee Borkman
- RE: fuse location and fbx_switch question chzumbrunnen
