Ticket #107 (new defect)

Opened 2 years ago

Last modified 1 year ago

Technical FAQ 4 fusebox.appinit.cfm

Reported by: scorfield Owned by: sean@…
Type: defect Priority: normal
Milestone: Web Site 1 Component: Web Site (fusebox.org)
Version: Severity: normal
Keywords: Cc:

Description

Mention skeleton application. Add in fusebox.appinit.cfm as well.

Attachments

Change History

Changed 2 years ago by kroche

Technical FAQ 4

What are fusebox.init.cfm and fusebox.appinit.cfm and why are they in some of the sample apps but not in the Core Files? Are either of them actually required?

The fusebox.init.cfm file was a new in fusebox 4.1. and fusebox.appinit.cfm is new in Fusebox 5.0. Both are "globals" files which can be used to initialise variables required at the start of a page execution. The first (fusebox.init.cfm) is included on every request, if it exists. It runs after the attributes are loaded, but before any fuseactions are run so you can do neat things with it like run security and change attributes.fuseaction for login. It's also a handy place to put your db settings. It's not "required" to run fusebox, but it is an "official core file." Note that the fusebox.init.cfm file replaces the need for using the old Globals plugin (although you can still use that w/ fusebox 4.1 if you care to). The second (fusebox.appinit.cfm) is included on the first request for a particular application, if it exists. It's also a handy place to initialise and application variables or instantiate CFCs.

Changed 1 year ago by scorfield

  • milestone set to Web Site 1
Note: See TracTickets for help on using tickets.