<SIGHS Type="Great Rejoicing">
Well, I finally figgered out the cause of my Verity problem.
</SIGHS>
When you set TYPE="File" in CFINDEX, the filename you use for
the KEY must apparently be fully qualified with the path as well.
My app is actually working now, but I have little hair left. <g>
The docs, I feel, are misleading. Although they say the KEY is the
"fully qualified path" when TYPE="Path", they simply say the KEY
is "Document filename" when TYPE="File". The fact that "fully
qualified" was used in referring to the Path type but not the File
type made me conclude, incorrectly, that the filename did not need
to be fully qualified. I had specified the path in the URLPATH
parameter, so incorrectly thought that would suffice.
What made things so confusing was that I had discovered by
accident that if I ran one CFINDEX using Type=Path, I could then
use a CFINDEX where Type=File. Apparently the fully qualified path
I specified in KEY when I ran the CFINDEX with TYPE=Path
switched the internal default path for Verity. I was just about ready
to throw out Verity as a quirky engine that didn't work. What a relief
to discover that the world actually works again <g>...
Gene Kraybill
On 4 Jul 2001, at 23:35, [EMAIL PROTECTED] wrote:
> I have an application that uses three Verity collections. I can
> successfully create the first collection and retrieve info from it, and
> can then do the same with the second collection. However, when I
> go back and do an update on the first collection, 2 error
> messages like the following are generated in file/sysinfo.log for each page I
>attempt to add:
>
> ----Start of error ----------------------------------
> Error E3-0422 (VDK 2): Could not find file Page_338.htm
>
> Error E3-0032 (VDK): No valid documents found in
> C:\WINNT\CFI70CB.tmp for collection
> E:\Web\worldwideguide\guides\verity\Guide_2_Pages\file
> ----End of Error ----------------------------------
>
> The contents of this update also do not show up in searches.
>
> This is my CFINDEX:
>
> <CFINDEX collection="#ThisCollection#"
> action="Update"
> type="File"
> key="Page_#ThisPageID#.htm"
> CUSTOM1="#ThisPageURL#"
> CUSTOM2="#ThisPageID#"
> extensions=".htm"
> language="English">
>
> Once this error occurs with a collection, I discovered that the only
> way I can correct it is to run the following code, taken in
> desperation from some sample CF code:
>
> <CFINDEX
> collection="#ThisCollection#"
> action="Refresh"
> type="PATH"
> key="#IndexDirectory#\"
> extensions="#IndexExtensions#"
> recurse="#IndexRecurse#"
> language="#IndexLanguage#"
> urlPath="#URLPath#\verity\Guide#Dev#_#GuideID#_PageLinks">
>
> Once I run the sample code, which does a PATH indexing
> operation rather than a FILE operation, I can then re-run the first
> CFINDEX and repopulate my collection (via a loop, file by file). The
> first CFINDEX does NOT have the same corrective effect, even if I
> change it to a Refresh rather than an Update.
>
> I've tried deleting, purging, repairing and optimizing, all to no avail.
> The only thing that seems to work is running the PATH-based
> refresh, then going back to my initial FILE-based indexing within a
> loop. The problem with that, of course, is that each time I must
> complete rebuild the collection, which will NOT be practical in the
> application I'm building.
>
> Any ideas greatly appreciated...
>
> Gene Kraybill
> LPW & Associates LLC
> Mansfield, PA
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
