If you just want regular stats, without the overhead of db logging in the
application, you can use what I call the "Generic wrapper" page, this also
solves the search engine and Verity problems with URL's.
The only overhead is that you need to create a directory with a single file
per each fuseaction - all files are identical you just need to copy the file
and rename it to the fuseaction.
Then all links need to point to fuseaction.cfm file instead of index.cfm.
The file is trivial:
<!--- Name: Generic Wrapper page
Description: Takes filename and based on it calls the index file with
correct action
written: 15/07/1999 NB
--->
<CFSET variables.TemplateName = GetFileFromPath(GetCurrentTemplatePath())>
<CFSET URL.FuseAction = listFirst (variables.TemplateName, ".")>
<CFINCLUDE template="../index.cfm" >
HTH,
Noam
You could write a custom logging tag that writes to a text file or a
db.
Have the tag also capture your fuseactions, too. Come to think of
it, I
already wrote this, it's called Tronny. I think it was Bjork who
expanded
greatly on this.
You wanna make a happy client, you develop your own custom logging
where the
client can view it right over the web as part of your app.
> A client is mad about server stats and with our fusebox app they
can't see
> specifically what pages are being hit... is there any software out
there
> to
> track this?... all that I have see so far just adds hits to the
index.cfm
> page time and time again... never any included or 'sub-pages'...
>
> Thanks for the input.
>
> je
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
