>
> As   far   as  you  can  download  that  application  try  to  change
> fusebox.SuppressErrors  flag  trying  to  avoid displaying/hiding that
> message.
>
> Do   you   see  that in the second example you don't see that message,
> but in the third one you do. Why? :-)
>


yes, because, generally speaking, the idea to have a
"fusebox.suppresserrors" flag was a poor one.
It was another thing that was decided last minute. The better thing to do is
just not to have the core
file handling errors at all.  Personally I would suggest that you do
<cfset fusebox.suppresserrors = FALSE> in your top level fbx_settings.cfm
file and just forget that that
API variable is there.  The problem is not so much a bug in the core as it
is that the core shouldn't be attempting to prevent mistakes on the
developer's part. In the Techspedition core file, the includes inside the
core are all TYPE'd as "missinginclude" so that only if the
file-to-be-included doesn't exist would the error be thrown (so if you have
a CF error in your code itself it won't cause a missinginclude error.)

The reason you don't see the error message during your example #2 is because
you have a ill-defined circuit whereas
in example #3 there is NO circuit defined.  Example #2 can be fixed by the
developer just making the needed change to either the XFA in question or to
the fbx_circuit.cfm file in the root of the app (depending on which one has
the mis-spelling). Example #3 can be eliminated simply by defining a default
fuseaction in your app -- the most popular way of doing that seems to be
putting
<CFPARAM name="attributes.fuseaction"
default="mydefaultcircuit.mydefaultfuseaction">
in the fbx_settings.cfm file in the root -- be sure to put in your own value
for the "default" attribute

==^================================================================
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
==^================================================================

Reply via email to