Andrew Mercer wrote:
so will Glamour have a solution for this issue?
dmFile and dmImage will both have status. So uploaded files that are draft will not be indexed by verity. The file index will be based on the dmFile object properties and not just a directory location. Ideally files should not be stored under the webroot then access to them can be more readily controlled.
How can search restrictions be applied to a file to match the object it is associated with?
What restriction are you after? Is this based on whether the parent object is live/draft?
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.
In Glamour you will be able to nominate a file as "not shared" and so the object will not be available as part of the general library.
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.
This is an option we are looking to eliminate. Assigning a file to any content type will record a reference to the object rather than just a link in the BODY text.
can a file uploaded to an object be used by another object??
Yes. 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/
