something like adding a list of objectIDs to custom3, then a t search time process those objects for publish / expiry date and permissions?

You have to remember that each users permission to access the documents will differ.

It is also possible that the viewable date/time may occure inbetween verity updates.

The other thing that needs to be monitored is the status of the object.

On 7/7/05, Jeff Coughlin <[EMAIL PROTECTED] > wrote:
Andrew Mercer 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?

Why not use one of the custom fields to add some kind of security info
to the indexed object?  Then when displaying the results you can verify
based on the custom field whether or not the user should see the
results.  This would likely require some core modification (or extend
the core), but its something to consider.

-Jeff C.

---
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/

--- 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/

Reply via email to