One solution, which I also use for other reasons, is what I call the
"generic wrapper" template:
Create a file like the following in a "search" sub directory of your fusebox
application
Generic Wrapper page:
<CFSET variables.TemplateName = GetFileFromPath(GetCurrentTemplatePath())>
<CFSET URL.FuseAction = listFirst(variables.TemplateName, "_.")>
<CFINCLUDE template="../index.cfm" >
Then copy the file each time renaming it as the fuseaction you want it to
perform.
Voila you have a directory with only the cfm's you want to index, and the
pain of maintenance is rather small all you have to do is copy the file and
rename it for each new fuseaction you add - I'm sure you could automate it
if you had enough fuseactions.
The cool thing is all files are *IDENTICAL* they just use the file name to
then perform the fuseaction.
In my case I also want to set the language so I add the line:
<CFSET request.DisplayLanguage = listGetAt(variables.TemplateName, 2, "_.")>
and then name the file:
Fuseaction_Language.cfm
Again generating the wrapper files for all languages is easy with a batch
copy command.
HTH,
Noam
----------
From: Ulf Unger [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, 24 October 2000 12:59
To: Fusebox
Subject: AW: Fusebox and Verity Search Engine
Hi Stephen, hi list,
but theres on problem - some of these pages don't get their content
from a
database. And I need these pages (with individual looking and
design)
indexed by the verity engine. The other things like
<cf_formurl2attributes>
etc. I've already done.
Is there a solution available?
Thanks
Ulf
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
