The current distribution of CCK 6.x-2 provides a new module from 5.x that sets view and edit permissions at the field level. Certain roles might be only able to see a few fields of all that is available on a content type and edit none while others might be able to edit a few of those.

Content permissions has one glaring flaw IMO, which has to do with the read-only view status of a field. Let's say, for example, you have permission to view all fields on a content type, but only edit a few. The view page will look like normal, and the edit page will only show those fields which you have permission to edit. What's missing in that picture? You can't see the read-only fields on the edit form. In the cases I use content permissions, seeing the values of the read-only fields is valuable context to know what to change in the editable fields.

Luckily, cYu wrote a patch that adds the values of the read-only fields back to the edit form. I think since yched is such a busy person, he would feel better if other people tested the patch to leave their experiences as well.

Workflow Fields is another module that can set fields to be invisible or read-only, but depending on workflow state, however it does not use the new CCK 6.x field permissions hooks. Instead, it tries to search through the form's FAPI array to find various field settings such as #access and #disabled along with changing to a markup field type to change the handling of content. While more powerful than Content Permissions with regards to workflow awareness, the implementation might benefit from some patching to utilize more of the new CCK field access hook since it has a known buggy history trying to support the various features of the Date widget.

Post categories

Drupal,
contrib