In 1.5.2 somebody changed the action for the cfindex call from Update to
Refresh. That means that if you're indexing multiple types that share a
property def, the last type to get indexed will be the ONLY type that turns
up in cfsearches using that property. And if the last type indexed has no
objects, then the collection will be empty.
The correct code for the cfindex call at the bottom of
cfa_propertyindexkeyupdate.cfm is:
<!--- Index property --->
<cfindex action=""> collection="#attributes.property#"
key="ObjectID"
type="CUSTOM"
title="ObjectName"
query="attributes.qPropertyData"
body="PropertyValue"
custom1="TypeID"
custom2="Property"
>
-----Original Message-----
From: Michael Conger [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2003 6:58 AM
To: Spectra-Talk
Subject: Verity Collections Empty
hey everybody, remember me?
I'm one of those poor lost souls that has been upgrading boxes from
CF4.5/Spectra1.5.1 to CFMX6.1/Spectra1.5.2
I've run into yet ANOTHER problem that's stumping me.
It appears that none of my verity collections are being indexed. I run the
spectra tags to reindex and everything seems to run without a problem, but
<cfsearch> returns no results whatsoever.
Any ideas? This is basically the last big hurdle we need to clear before
putting this whole big mess into production. Please help!
ps. I have built a few non-spectra verity collections on the same box and
they all work fine. Just fyi.
THANKS,
Michael Conger
[EMAIL PROTECTED]
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
