So give that, if the files are uploaded to a directory with the objectID in www\files\ then the verity index can be modified to pass that pathname in for searching.
online help attached.
Then the external file collection can point to www\files with no recurse for all publically accessable documents.
Any one care to comment on this approach?
On 7/7/05, Andrew Mercer <[EMAIL PROTECTED]> wrote:
When verity is configured to search documents, you point it at a directory - works fine.
You can upload a document to an object - works fine
When you create a far cry object, you can set publish and expiry dates and can control the permissions to control access - works fine
But if verify search finds a document, any one can view it - irrespective of any properties set against the object it is attached too - not so fine
Has any one got a solution or can suggested a why such that the search results for documents attached to an object cohere to the same restrictions as the object itself?
<!--- EXAMPLE # 5 Index a PATH within a QUERY. ---------------------------->
<!--- Retrieve a row with a column that contains a path (Project_Docs). --->
<cfquery name="getEmps" datasource="cfdocexamples">
SELECT * FROM EMPLOYEE WHERE Emp_ID = 15
</cfquery>
<!--- Update the collection with the above query results. --->
<!--- key specifies a column that contains a directory path. --->
<!--- path is indexed in same way as if no query involved. --->
<cfindex
query="getEmps"
collection="CodeColl"
action="update"
type="path"
key="Project_Docs"
title="Project_Docs"
body="Emp_ID,FirstName,LastName,Project_Docs">
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
