Let me first explain a little about the site.
It is an entertainment news, review, online store - providing news, reviews etc. about films, videos, music, games, tv ... anything to do with the entertainment industry.
It will be included in the list of sources for Google News.
It will have about 80 news contributors as well as the site admin/editors/publishers. These news contributors will probably not be able to authorise the content.
The news contributors will be able to create news items, events and links about whatever stories they like. What I need to provide is a mechanism for them to link content items together, this could be achieved by extending the dmNews and bringing in aRelatedObjectIDs within the existing maintenance sections. But what i wish to do is provide a hierarchical structure to the news. Then using the built in getSiblings, getAncestors, getChildren etc i will be able to provide related content links when a news story is displayed. This is why i think it is best to let them add through the tree, it is using so much of the in-built functionality of Farcry.
I have created a new node of the root, called content - i really liked the way that this automatically created a new sub-tab under the site tab similar to files and images - very sweet. The news contributors will have access to create content in this area only, this is achieved by permissions.
This all works, but what i would like to do is "hide" the links to create html, css, flash, includes from these news contributors. I know a bit of training and they "should not" create content of these types.
Example of a simple news story hierarchy, this hierarchy will grow as new "stories are added".
root
-Content
--News Item: A new James Bond film is announced
---Event Item: Film production to start
----News Item: more news about film production....
---Link to official film website
---News Item: Actor list...
----News Item: Story about one of the actors on the film
----News Item: Story about another actor on the film
---Event Item: Film premiere
----News Item: covering the film premiere
Hope this all makes sense.
Chris.
Geoff Bowers wrote:
Chris Kent wrote: ...snip...8<...
This works perfectly, but I would like to remove the options to dmHTML, dmFalsh, dmCSS, dmInclude from a Group of contributor users, just allowing them to create dmNavigation, dmNews, dmLinks, dmEvents, dmImage and dmFile. These options will still remain for other users who have access to the tree.
...snip...8<...
I have looked through all the policy group permissions, but can not see one that will allow me to restrict these types by Policy Group.
I do not wish to change core to archive this. Does anyone have any suggestions.
I don't think we ever envisaged this sort of use. The tree permissions work on a pretty clever inheritence model that is really designed to allow contributors with access the ability to add whatever content types. The point is to restrict where they can contribute and not what. You can of course require another group to approve that content.
Your effectively saying you want a permission that allows different groups access to see certain content types in the tree, in addition to the permission to create/edit/approve. Can you explain from a "use case" point why you need this?
Would one of your contributors potentially beable to add dmNews in one section of the tree but then not in another? Or is this an all or nothing permmisson on the content type?
Can you clarify why you are getting contributors to add news through the tree and not through the use of standard News Admin and publishing rules?
Apologies for all the questions -- it's important for our team to understand what motivates developers to change the way things were originally designed. We trying to work out if we're not communicating enough or if the code base needs to be changed.
-- 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]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
