Just a wild guess here: The file in question is being <cfinclude>d and the variables it is setting are getting set into the Application.cfc's variables scope, and therefore unavailable elsewhere.
On Mon, Nov 5, 2012 at 2:19 PM, Nick Gleason <[email protected]> wrote: > > Hi folks, > Bit of a head scratcher here which I'm hoping may be obvious to you all. > We've got a Fusebox 3 application which we have recently converted from > application.cfm to application.cfc. > One puzzling result has been that during a single page request, an > "attributes" variable that is set in a file called from application.cfc > (and formerly from application.cfm) is no longer present once we get down > the line in the code flow to displaying the page. That is, when we go back > to application.cfm, the variable is available down the line for the page > display. But, when application.cfc is used, the variable is available when > it is first called and set, but then has disappeared by the time the page > flow gets to the file where the page display is done. > So, it seems that some variables in a single request are not as persistent > with application.cfc, at least in a FB 3 context? That seems surprising > but I can't really come up with another explanation. And, so far, we > haven't been able to figure out exactly where or why the attributes > variable is getting dropped. > Any thoughts? > Nick > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:353066 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
