This seems to be more elegant than what I have built thus far but it also
seems like more work.
What I have written so far will create a temp folder wherever you tell it
to, then search through you site beginning where you tell it to and recurse
if you want. It finds only the dsp files (since they are where the static
content is anyway) and copies them to the temp folder in a structure
identical to your site. Then the indexing begins. This may sound like a lot
but it really is quite fast.
The problem I have run into is trying to associate a fuseAction with each
file that is indexed. So far I have been using a custom tag that you call at
the top of each dsp file (this is the part I do not like) and it accepts the
fuseaction used to call that file as an attribute. It will also take a page
title if you use dynamic titles. If you search you will get the link to the
page directly, but the custom tag will redirect you to the index page in
that circuit and pass the fuseaction associated with it.
So far I have been quite happy with the ease of use. However, I do not like
having to use the custom tag call in every dsp page. This takes away from
the ease of use of the app I have written.
Maybe some good solutions will come up in the discussion tonight and this
thing will become reality!
Russ
-----Original Message-----
From: Eron Cohen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 2:37 PM
To: Fusebox
Subject: RE: Verity
Tom,
(forgive my paste-age)
One way to do it is:
1) Keep a list of fuseactions in a database table
(this is something I do by default)
2) Loop through the fuseactions and use CFHTTP to grab
the pages that result from each fuseaction
3) Make a "fake" query useing Querynew, QuerySetCell,
and QueryAddrow.
4) Use CFINDEX to index the fake query, the key or a
custom field is going to be the fuseaction so that
when someone searches, they can be dumped back to the
correct fuseaction.
Because this can be a slow process, you might want to
use some kind of timestamp to keep track of what pages
have been updated and which ones not. Only index the
ones that have not been updated "Recently"
There are other ways to do it, but this is one, and it
does work.
Eron
-----Original Message-----
From: Tom [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 2:00 PM
To: Fusebox
Subject: Verity
So, has anyone developed a solution for the Verity
issue? I went and built a
fuseboxed app and now I'm in trouble cuz I can't build
a search for it. I
noticed a search app built in fusebox in the Allaire
developer exchange.
Does it solve the problem?
-Tom
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
