Aengus Lawlor wrote:
> I've set up the form interface to Analog on a colleagues website, so
> that they can keep an eye on the usage patterns on a new website.
>
> The form uses the "cg" variable to point at a .CFG file where Various
> defaults have been set, including FILEEXCLUDEing all the FrontPage
> entries, images, and stylesheet requests.
>
> FILEEXCLUDE *_vti*,*.jpg,*.gif,*.css
>
> Of course this causes Analog to do an implicit FILEINCLUDE on everything
> first, so that when you try to use the "Only certain files" section of
> the form to restrict the analysis to just a single file, or
> subdirectory, it doesn't work, because the implicit FILEINCLUDE also
> includes everything else. I can do that restricted analysis by putting
>
> FILEINCLUDE /some/file
>
> in the CFG file before the FILEEXCLUDE, but that's a bit more work than
> the user wants to do.
>
> I can also make it work by removing the FILEEXCLUDE from the CFG file,
> and making it the default value for the FILEEXCLUDE field in the form
> instead, but I'd rather keep all the default settings in the CFG file,
> so that if I'm asked to look at this form again in 6 months, I don't
> have to remember that there's a setting way down at the bottom of the
> form where I never look that's causing a change!
>
> Any suggestions
How about adding the FrontPage file excludes into a new config file and
adding it as the last entry in the form (in a hidden 'cg' field). I'm not
sure that all browsers maintain form item order, but it's worth a try.
HTH,
Jeremy Wadsack
Wadsack-Allen Digital Group
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
