Date:  03/17/2008 06:58:41 PM Msg ID:  003707
From:  FoxWeb Support Thread:  003698
Subject:  Re: \"Script \"index.fwx\" is invalid or no
The first thing I would do is test the hypothesis that FoxWeb is unable to see index.fwx.  To do so, you could write a FoxWeb script (with a name other than index.fwx) that tries to access index.fwx the same way that FoxWeb does.  FoxWeb uses the ADIR function with an extension of * to find all files that match the script name.  For example, in your case you would run:

ADIR(aFileList, "index.*")

You could then traverse the array to find out whether index.fwx is visible to FoxWeb channels.  If the file is visible, you could even try to compile it with the fwCompile object to see if there are problems in the compilation process.
FoxWeb Support Team
support@foxweb.com email
Sent by David Hempy on 03/17/2008 02:27:25 PM:

Any other suggestions?  I now have three files (two index.fwx files and a guest_list.fwx file) that are exhibiting this behavior.  Other files regenerate just fine. 

I've asked our network sysadmin to look at this and see if it's some kind of OS problem.  Different things indicate that it is the OS, Apache, or FoxWeb at different times, and I've been unable to determine where the breakdown is occurring.

Does FoxWeb have any sort of aggressive debugging mode, where it logs fussy details like "found index.fwx"; "opened index.fwx", "generated index.prg", etc.?

 -dave