This is kind of a hack on what you need to do, but I had the same problem.
I had static dsp_ pages intersperced with dynamic dsp_ pages in most of my
directories. I tried a number of ways to resolve it, most of them have
already been mentioned. I had about 60 templates on the site that were
static, so I set up a seperate collection and did the following.
First, instead of using refresh, I set a "purge" action at the beginning of
the index template. I used type=path, and started from the root directory.
This way I purged all the templates in the index. (see code below)
<cfindex action="purge" collection="#o_collect#" type="path"
key="#PathRoot#" recurse="yes">
Then I manually had to insert each record into the index. I did this using
the action="update" and type="file". I pointed the key to the directory
mapping of where the file was located, and then I used the custom field to
assign my url mapping with appropriate fuseactions and variables. (see code
below)
<cfindex action="update" collection="#o_collect#" type="file"
language="#indexLanguage#" extensions="#indexExtensions#"
recurse="#indexRecurse#"
key="#PathRoot#financial\dsp_grant_instr.cfm"
custom1="#linkRoot#financial/grant.cfm?fuseaction=instructions"
>
Since verity organizes everything in Descending order, you will have to put
the templates you want the search results to show first towards the end of
the template. This may not be what you are looking for, but I feel that I
have the most control over what gets put into the index. The only other
easy way is to place a cfif statement in each one of your display templates
(including your dynamic templates) and then index the entire directory path.
<cfif #cgi.script_name# contains dsp_somepage.cfm>
<cflocation url="index.cfm?fuseaction=someaction">
</cfif>
HTH,
David Henry
HPER Technology Services
School of Health, Physical Education and Recreation
Indiana University
(812)855-4270
[EMAIL PROTECTED]
-----Original Message-----
From: Ulf Unger [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 24, 2000 5:11 AM
To: Fusebox
Subject: Fusebox and Verity Search Engine
Hi,
I have the following problem:
In a web application I use several user-defined "dsp_" files which must be
searchable for der Verity engine. But these "dsp_" files use several
variables which aren't available (but necessary for the information). No
when I use the search results from verity these results link directly to the
"dsp_" files and not to the index file with the correct fuseaction. Are
there any solutions available?
I've thought about a solution like:
<cfif NOT IsDefined("ATTRIBUTES.fuseaction")> .... but wouldn't this
increase the processing time for each template?
Please help me :-)
Thanks in advice
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.
------------------------------------------------------------------------------
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.
