Related links should only be revealed in the presentation layer if the content is approved. Therefore relating DRAFT content is not necessarily a bad thing -- some might argue it is a dinstinct advantage.
In any event I can't sanction modifications to the core code base that enforces this type of behaviour -- if anything it needs to be a configurable option. Especially since changing the current approach may adversely impact the business process of existing sites.
It sounds to me as though we need an additional tree permission such as VIEWINDRAFT rather than modifications to the display.cfm tag.
-- geoff http://www.daemon.com.au/
Gary Menzel wrote:
But presumably the user can still browse to the DRAFT content through the presentation layer navigation?? Stil not sure of the business requirement here.
I have spoken to Andrew on the phone today regarding this. Here (as I see it) is his requirement:
There are multiple contributor groups (lets say Group A and Group B to keep it simple).
Group A contributes to one branch of the tree.
Group B contributes to a separate branch of the tree.
When items from Group A's tree are in DRAFT only Group A people should be able to see them - and vice versa.
That is: DRAFT content is only visible by those who have permission to see it and those permissions are not related to any public VIEW permissions (because, ultimately, the content is viewable by anyone).
When the content from either groups tree is APPROVED it is visible to everyone.
This is not an unreasonable requirement. In a Public Service environment this would be mandatory. You would not want people from one group linking to content in the other group until it was APPROVED.
Hope this helps clarify things.
Regards, Gary Menzel
--- 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/
