Andrew Mercer wrote:
something like adding a list of objectIDs to custom3, then a t search time process those objects for publish / expiry date and permissions?
As files can be attached to more than one object, its not so easy to just eliminate files from the system because one of the pages linking to it has expired.
There are however plenty of opportunities to provide checks against these sorts of files.
For example, you might use the download.cfm file to run some conditional logic to check if the file is associated with a content item that has expired and effectively removed from the system. This does not require any core modification and allows you to fire any logic prior to delivering files.
Hope that helps, -- geoff http://www.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/
