Yah Erik, that's what I had in mind, I just wanted to stick with 100% fusebox. I also need to include some of the fbx_settings. I wonder if I should just CFMODULE an empty fuseaction at the beginning of the non-fusebox file, just so I have all the vars available.
So for example, in the search.cfm file add: <cfmodule template="index.cfm" fuseaction="common.getSettings"> Some code goes here... <CFFLUSH> Lengthy processing code goes here. How does it look? - Sivan -----Original Message----- From: Erik Voldengen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 2:41 PM To: [EMAIL PROTECTED] Subject: FW: FB3 core kills CFFLUSH... ever. (example app) Here's something Erki came up with last time this issue came up. > -----Original Message----- > From: Erki Esken [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 15, 2001 3:39 PM > To: [EMAIL PROTECTED] > Subject: Re: FB3 core kills CFFLUSH... ever. (example app) > > > And it works.. Attached is a simple searching app that uses the > technique I outlined. > > Erki > > Conference in a Box -- available at: > www.halhelms.com (under STORE) > > Want to help plan next year's conference? > http://www.halhelms.com/index.cfm?fuseaction=conference.volunteer > > ==^================================================================ 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 ==^================================================================
