From the sounds of it you don't want to use fusebox.init.cfm for your
processing code, you want to use fusebox.appinit.cfm instead.
fusebox.apppinit.cfm is actually designed for this very purpose: it is
executed (if found) at the very beginning of the request only when the
Fusebox is loaded or reloaded. People typically use it to initialize
application-level variables but it'll work for this too I'm sure.

You should be able to just cut out your current processing code from
fusebox.init.cfm and paste it into a new file. Then save that file as
fusebox.appinit.cfm and you're done. You won't need any conditionals
testing the state of the Fusebox load, since any code in
fusebox.appinit.cfm is only processed if fusebox.load is true. You can
just go straight to your handler code.

HTH

Mike
http://www.fusebuilder.net


--- In fusebox5@yahoogroups.com, "neobob182" <neobob182@...> wrote:
> Hey Josh,
>
> My issue isn't so much handling the pages, it's just that I need to
> include the fusebox.init.cfm only once after I restart the Fusebox
> application files. After the initial include of Fusebox.init.cfm, my
> layout will throw function errors because it has already been
> declared. I am looking for a variable (Sean listed a few) that I can
> put in a cfif statement to run the Fusebox.init.cfm only once.
> However the variables that were given don't flag at 1, they must get
> set to true after the Fusebox application is restarted and then never
> returned to false. Which creates a problem with my cfif statements
> because I only want them to run once after a restart. I'm just
> wondering if there is a way to flag the cfif statement with these
> variables so that it is only true once after the Fusebox application
> has been restarted (which isn't going to happen very often)
>
> Thanks,
> Jody
>