It is a CF thing.  CF doesn't like 0k files.  It's actually
got nothing to do with Fusebox.

Try it with an application.cfm file if you'd like to experiment.

-Erik


> -----Original Message-----
> From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, May 25, 2002 1:14 PM
> To: [EMAIL PROTECTED]
> Subject: Re: FB Core and CF 4.5.1
>
>
> So you guys/gals are serious that an empty file can cause an
> error?  What is
> that from?
>
> ----- Original Message -----
> From: "hal helms" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, May 25, 2002 4:08 PM
> Subject: RE: FB Core and CF 4.5.1
>
>
> > No, because they're in CF comments, leaving the actual file size 0 k.
> >
> > -----Original Message-----
> > From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, May 25, 2002 4:01 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: FB Core and CF 4.5.1
> >
> >
> > the fusedocs are there isn't that good enough?
> >
> > ----- Original Message -----
> > From: "John Beynon" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Saturday, May 25, 2002 3:45 PM
> > Subject: RE: FB Core and CF 4.5.1
> >
> >
> > > CF can't cope with 0Kb files I'm pretty sure...put a comment tag in
> > > your fbx_settings and that should solve it,
> > >
> > > John.
> > >
> > > > -----Original Message-----
> > > > From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]]
> > > > Sent: 25 May 2002 20:03
> > > > To: Fusebox List
> > > > Subject: FB Core and CF 4.5.1
> > > >
> > > >
> > > > I developed a site on CF MX and I uploaded it to test on the server
> > > > it will be running which is running CF 4.5.1 and I get the following
> >
> > > > error which I think might be a FB Core problem:
> > > >
> > > > Error Diagnostic Information
> > > > Just in time compilation error
> > > >
> > > > unknown context error reached at the end of the CFML templateInvalid
> >
> > > > expression format. The usual cause is an error in the expression
> > > > structure.
> > > >
> > > > The last successfully parsed CFML construct was the CFML template
> > > > beginning occupying document position (1:1) to (1:1).
> > > >
> > > > The specific sequence of files included or processed is:
> > > > D:\INTERNET\CLIENTS\MINOGUE\INDEX.CFM
> > > >   D:\INTERNET\CLIENTS\MINOGUE\FBX_FUSEBOX30_CF45.CFM      CFInclude
> > > >     D:\INTERNET\CLIENTS\MINOGUE\PRODUCTS\FBX_SETTINGS.CFM
> > > >  CFInclude
> > > >
> > > > The error occurred while processing an element with a general
> > > > identifier of (CFINCLUDE), occupying document position
> > > > (220:4) to (220:63).
> > > >
> > > > The error occurred while processing an element with a general
> > > > identifier of (CFRETHROW), occupying document position
> > > > (224:12) to (224:22).
> > > >
> > > > -------------------------
> > > >
> > > > Has anyonre encountered this problem before.  Do you know what it
> > > > might be related to?  You know the solution to problem.  Basically
> > > > the problem only occurs when I leave the root directory.  My
> > > > FBX_Settings file is empty in subdirectory.
> > > >
> > > >
> > > >
> > > > ____________________________________________________________________
> > > > _
> > > > This message has been checked for all known viruses by UUNET
> > > > delivered
> > > > through the MessageLabs Virus Control Centre. For further
> > > > information visit http://www.uk.uu.net/products/security/virus/
> > > >
> > >
> > > _____________________________________________________________________
> > > This message has been checked for all known viruses by UUNET delivered
> >
> > > through the MessageLabs Virus Control Centre. For further information
> > visit
> > > http://www.uk.uu.net/products/security/virus/
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>

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