Closed (won't fix)
Project:
Content Construction Kit (CCK)
Version:
6.x-2.1
Component:
Content Permissions module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Jan 2009 at 16:12 UTC
Updated:
18 Dec 2009 at 18:58 UTC
Comments
Comment #1
Rosamunda commented.... bump?
Comment #2
dlx commented+1
Comment #3
dlx commentedActually, version 6 needs this functionality badly too.
Comment #4
karens commentedThe 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. You can also use the Permissions API with the new module I just contributed at #503118: Add easy reset form to user permission page, which makes it easy to do mass changes to all those field permissions on the permissions screen.
Comment #5
Grayside commentedI have this functionality in a new module just now. I'll see about making it available.
Comment #6
csc4 commented@Grayside: would love to see your module as could use a lot of help with permissions. Seems ATM setting View doesn't let you see fields on Edit forms and I can't figure out why not.
I can't seem to figure out how to set default values and allow users to see things on the edit page unless you use Node Reference fields which surely can't be right?
Comment #7
Grayside commented@csc4 View permission is distinct from Edit permission. You only see a field on a node edit form if you have edit permission. Default field values are set in the field definition by the Administrator.
Field Permissions Plus is now available and stable if you would like to test it out.
Comment #8
Rosamunda commentedThanks!!
Comment #9
markus_petrux commentedFor the record: as discussed in #501404: Field Permissions in Core, field permissions in core has been postponed for D8. In the meantime, this feature will be implemented by Field Permissions module, which also has a version for D6 that implements field permissions on demand (from field settings form), and you can enable permission types like: create field, edit field, edit own field, view field and view own field. These permissions are not enabled by default, so the Permissions Administration screen has only the permissions that you really need.
Comment #10
BenK commentedSubscribing...