see http://www.tejasa.com/node/167:

This role/permission based model is not the only way that people want to restrict fields. One other use case is to restrict fields based on the workflow state of the node. For example, the Issue field is only available if the article is in 'editor approved' state or higher. All of the pieces are now available to whomever wants to write that module. When you do, please contribute it!

and http://drupal.org/node/63240

i have a module that restricts field access by role and workflow state in a 4.7 system, will port it to work with the new cck and views alongside moshe's new permissions module.

Comments

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented

subscribe

karens’s picture

karens commented
Version: 6.x-1.x-dev » 6.x-2.x-dev
Component: General » Content Permissions module

Bump to 6.2.

karens’s picture

karens commented

I think the best route forward to make field permissions easier to set up would be to use http://drupal.org/project/permissions_api, then write some wrapper code to do some of these custom things using that API.

This could be a separate contrib module or a patch to the core module that would work if the Permissions API is installed. If someone wants to create such a thing, that would be great. I suspect none of the CCK maintainers has time to do this.

mitchell’s picture

mitchell commented

Subscribe

karens’s picture

karens commented
Status: Active » Closed (won't fix)

The number of permission elements is already huge and overwhelming, we probably won't add any more in the core module. There is nothing to prevent anyone who wants to create a separate Content Permissions Plus module from doing so and adding additional features in.