Absolutely I will. I was just hoping I could persuade a little more fuseQ out of you. :)
-----Original Message----- From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]] Sent: Monday, June 10, 2002 11:25 AM To: [EMAIL PROTECTED] Subject: Re: possable fuseQ core error no differently than, say, the <cfdefaultcase> tag, except that you could have "bubbled" the error up. I'm not sure the error that occured is the type of error one wants to spend a lot of time "trapping" -- usually you want to trap problems in the code (in FB that means problems in the fuses) rather than something like you just encountered -- let's face it, the next time you see the same cfdefaultcase error you're gonna first look for undefined fuseactions, right? ----- Original Message ----- From: "Brian J. LeRoux" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 10, 2002 2:10 PM Subject: RE: possable fuseQ core error > doh! Thanks John. I should've left well alone and approached the problem a > day later. Ah well.. that defaultcase flag should've been a bigger clue. > > Thanks again, > Brian > > ps. > Would the fuseQ nested exception handling technique thats been dangling > *just* in front of our noses catch this kind of error? If so how would we go > about implementing this? ;) ;) *nudge* *nudge* > > -----Original Message----- > From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 10, 2002 5:01 AM > To: [EMAIL PROTECTED] > Subject: Re: possable fuseQ core error > > > Brian, > > in circuit "home" you have a Fuseaction of "checkpermissions" yet in > circuit "Mail" you're referring to "home.permissions" a la: > > I bet things will work if you change that to > "home.checkpermissions" > > [From experience, Brian, a general rule of thumb is that if one *thinks* it > is a core file problem, then it's probably not. That doesn't mean there > cannot be errors in core files but rather that core file problems tend to > manifest themselves very subtlely -- they don't call out their own error via > a <cfdefaultcase> and the like. Core file errors will *look like* human > errors; Human errors will *look like* core file errors. So whichever one you > *think* you have, that it's likely the opposite.] > > > > ----- Original Message ----- > From: "Brian J. LeRoux" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, June 10, 2002 2:10 AM > Subject: RE: possable fuseQ core error > > > > Sorry (and thank you for responding), I'm nesting the circuits to achieve > > the layout and heres the code: > > > > Home switch: > > <cfcase value="checkpermissions"> > > <cfinclude template="act_check_permissions.cfm"> > > </cfcase> > > <cfcase value="applylayout"> > > <cfset attributes.suppresslayout = "No"> > > </cfcase> > > > > Home fbx_circuits: > > <cfset fusebox.circuits.CustomerService = "home/CustomerService"> > > <cfset fusebox.circuits.Mail = "home/CustomerService/Mail"> > > > > Home cicuit fbx_layouts: > > <cfif attributes.suppresslayout> > > <cfset fusebox.layoutfile = ""> > > <cfelse> > > <cfset fusebox.layoutfile = "lay_admin.cfm"> > > </cfif> > > > > The mail circuit fbx_switch: > > <cfcase value="main"> > > <cfparam name="inbox" default="Inbox"> > > <cfset AddToQ(' home.permissions ')> > > <cfinclude template="qry_getUserAccounts.cfm"> > > <cfinclude template="dsp_main.cfm"> > > <cfset AddToQ(' home.applylayout ')> > > </cfcase> > > ---------------------------- > > I don't know if this helps much / thnanks for your input- > > Brian > > > > -----Original Message----- > > From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, June 09, 2002 7:25 PM > > To: [EMAIL PROTECTED] > > Subject: Re: possable fuseQ core error > > > > > > brian, > > I cannot help too much without seeing the code, esp since I can't tell if > > you're doing FB3 nested layouts or FuseQ layout fuses. > > > > ----- Original Message ----- > > From: "Brian J. LeRoux" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Sunday, June 09, 2002 7:57 PM > > Subject: possable fuseQ core error > > > > > > > Heres the scenario, I've a directory stucture / circuits like this: > > > > > > home > > > |--CustomerService > > > | |-Mail > > > | +-Search > > > |--SomthingElse > > > > > > > > > Pretty basic. The home application defines a simple security module. One > > of > > > the fuseactions as you can guess is checkPermissions. I'm using fuseQ to > > > check permissions in all the child circuits throughout the application > > > without a problem however in the mail circuit for whatever reason I call > > > mail.main and it wraps the first layout without consequence but nests > > inside > > > it the classic, "This is the cfdefaultcase tag. I received a fuseaction > > > called "Mail.main" and I don't know what to do with it." BUT THEN it > puts > > > the proper mail.main content inside the next layer. > > > > > > Heres whats even more weird, in the home circuit (and cascading > throughout > > > the children)I have the following: > > > <cfset fusebox.suppresserrors = false> > > > > > > *brian is confused* > > > > > > I changed the verbage of the cfdefaultcase tag in each circuit to > include > > > fusebox.circuitName to check where the error was coming from and it is > the > > > home circuit freaking out... > > > > > > What am I missing? > > > > > > > > > > > > > > > > > > > > > > > > ==^================================================================ 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 ==^================================================================
