How can search restrictions be applied to a file to match the object it is associated with?
Anything added to the CMS needs to be considered to be content and therefore handled in the same manner. When a file is associated with an objected (uploaded in the PLP file step) it needs to be considered a part of the object's content, and not some external entity with no relationship to the object.
when a file is uploaded durring the PLP process, the dmFile objectID is stored in <object>_aObjectIDs
Another file that is 'inserted' from the tree or elsewhere (what other options are there?) are NOT stored in this table.
can a file uploaded to an object be used by another object??
On 7/11/05, Geoff Bowers <[EMAIL PROTECTED]> wrote:
Andrew Mercer wrote:
> If a file is uploaded to an object (not a file loading into file of the
> site tree), then I think it is safe to say that file belongs to that
> object.
This may appear the way things are from the current user interface for
FarCry 2.3. However, the File objects can have any number of
associations and frequently do in custom object implementations. But
most significantly the Glamour project introduces much more universal
access to media assets, effectively dispensing with the tree management
of files in preference for a categorised library approach.
-- 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/
--- 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/
